PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-functions.html
Example 19.3 Selecting the most up-to-date replica for manual failover The stored function GTID_UNION() can be used to identify the most up-to-date replica from a set of replicas, in order to perform a manual failover operation after a source server ... This section provides examples of stored functions (see Chapter 27, Stored Objects) which you can create using some of the built-in functions provided by MySQL for use with GTID-based replication, listed here: GTID_SUBSET(): Shows whether one GTID set is a subset of ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-lifecycle.html
The replica verifies that no thread has yet taken ownership of the GTID in gtid_next in order to process the transaction. On a multithreaded replica (with replica_parallel_workers > 0 or slave_parallel_workers > 0 ), transactions can be applied in ... The life cycle of a GTID consists of the following steps: A transaction is executed and committed on the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options-reference.html
replica_preserve_commit_order: Ensures that all commits by replica workers happen in same order as on source to maintain consistency when using parallel applier threads. slave_preserve_commit_order: Ensures that all commits by replica workers happen ... The following two sections provide basic information about the MySQL command-line options and system variables applicable to replication and the binary ...
https://dev.mysql.com/doc/refman/8.0/en/semijoins.html
An ORDER BY clause is permitted but ignored, since ordering is irrelevant to the evaluation of semijoin strategies. A semijoin is a preparation-time transformation that enables multiple execution strategies such as table pullout, duplicate weedout, ...
https://dev.mysql.com/doc/refman/8.0/en/slow-query-log.html
mysqld writes a statement to the slow query log after it has been executed and after all locks have been released, so log order might differ from execution order. The server uses the controlling parameters in the following order to determine whether ... The slow query log consists of SQL statements that take more than long_query_time seconds to execute and require at least min_examined_row_limit rows to be ...
https://dev.mysql.com/doc/refman/8.0/en/working-with-null.html
When doing an ORDER BY, NULL values are presented first if you do ORDER BY ... The NULL value can be surprising until you get used to it. Conceptually, NULL means “a missing unknown value” and it is treated somewhat differently from other ...
https://dev.mysql.com/doc/refman/8.0/en/xa-restrictions.html
If the transaction is not empty, the replica is able to continue running, but you should take steps to discontinue the use of replication filters with XA transactions in order to avoid potential issues. If two XA transactions committed in parallel ... XA transaction support is limited to the InnoDB storage ...
https://dev.mysql.com/doc/refman/8.0/en/audit-log-filter-definitions.html
If the function does take arguments, an args item is needed, and the arguments must be given in the order listed in the function description. For information about using JSON data in MySQL, see Section 13.5, “The JSON Data Type”. Filter ...
https://dev.mysql.com/doc/refman/8.0/en/audit-log-logging-configuration.html
In this case, the file name has .gz and .pwd_id.enc suffixes added, corresponding to the order in which those operations occur. This section describes how to configure audit logging characteristics, such as the file to which the audit log plugin ...
https://dev.mysql.com/doc/refman/8.0/en/binary-varbinary.html
All bytes are significant in comparisons, including ORDER BY and DISTINCT operations. All bytes are significant in comparisons, including ORDER BY and DISTINCT operations. The BINARY and VARBINARY types are similar to CHAR and VARCHAR, except that ...