Search Results
https://dev.mysql.com/doc/refman/8.4/en/replica-logs.html
A replica server creates several repositories of information to use for the replication process: The replica's relay log, which is written by the replication I/O (receiver) thread, contains the transactions read from the replication source server's ...
https://dev.mysql.com/doc/refman/8.4/en/replication-administration-pausing.html
You can stop and start replication on the replica using the STOP REPLICA and START REPLICA statements. The I/O (receiver) thread continues to read events from the source but they are not executed. This makes it easier for the replica to catch up ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-blackhole.html
The BLACKHOLE storage engine accepts data but discards it and does not store it. When performing binary logging, all inserts to such tables are always logged, regardless of the logging format in use. Updates and deletes are handled differently ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-create-alter-drop-server.html
The statements CREATE SERVER, ALTER SERVER, and DROP SERVER are not written to the binary log, regardless of the binary logging format that is in use.
https://dev.mysql.com/doc/refman/8.4/en/replication-features-current-user.html
In some cases, such as statements that change passwords, the function reference is expanded before it is written to the binary log, so that the statement includes the user name. For all other cases, the name of the current user on the source is ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-floatvalues.html
With statement-based replication, values are converted from decimal to binary. Because conversions between decimal and binary representations of them may be approximate, comparisons involving floating-point values are inexact. This is true for ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-flush.html
Some forms of the FLUSH statement are not logged because they could cause problems if replicated to a replica: FLUSH LOGS and FLUSH TABLES WITH READ LOCK. The FLUSH TABLES, ANALYZE TABLE, OPTIMIZE TABLE, and REPAIR TABLE statements are written to ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features.html
The following sections provide information about what is supported and what is not in MySQL replication, and about specific issues and situations that may occur when replicating certain statements. Statement-based replication depends on ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-functions.html
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 ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source-provision-replica.html
If the sources in the multi-source replication topology have existing data, it can save time to provision the replica with the relevant data before starting replication. In a multi-source replication topology, cloning or copying of the data ...