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-delayed.html
Note START REPLICA and STOP REPLICA take effect immediately and ignore any delay. MySQL supports delayed replication such that a replica server deliberately executes transactions later than the source by at least a specified amount of time. This ...
https://dev.mysql.com/doc/refman/8.0/en/replication-encrypted-connections.html
Note In MySQL 8.0.16 through 8.0.18, MySQL supports TLSv1.3, but the SOURCE_TLS_CIPHERSUITES option is not available. To use an encrypted connection for the transfer of the binary log required during replication, both the source and the replica ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-differing-tables.html
Note Replication between tables which are partitioned differently from one another is not supported. Source and target tables for replication do not have to be identical. A table on the source can have more or fewer columns than the replica's copy ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-errors.html
Note If a temporary error is recorded in the replica's error log, you do not necessarily have to take any action suggested in the quoted error message. If a statement produces the same error (identical error code) on both the source and the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-invoked.html
Note Attempting to replicate invoked features using statement-based replication produces the warning Statement is not safe to log in statement format. Replication of invoked features such as loadable functions and stored programs (stored procedures ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-load-data.html
When binlog_format=STATEMENT is set, note that LOAD DATA does not generate a warning, unlike other unsafe statements. LOAD DATA is considered unsafe for statement-based logging (see Section 19.2.1.3, “Determination of Safe and Unsafe Statements ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-memory.html
Note that the replica still has outdated data in a MEMORY table during the interval between the source's restart and its first use of the table. When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-shutdowns.html
Note that the durability of transactions is still not guaranteed with this setting, because operating systems or disk hardware may tell mysqld that the flush-to-disk operation has taken place, even though it has not. It is safe to shut down a ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-transaction-inconsistencies.html
Note that this is harmless if GTIDs are enabled (however, in that case it is not recommended to use --dump-replica or --dump-slave). Inconsistencies in the sequence of transactions that have been executed from the relay log can occur depending on ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-assign-anon.html
Note that as is standard for MySQL replication, this feature does not support replication from MySQL source servers earlier than the previous release series, so MySQL 5.7 is the earliest supported source for a MySQL 8.0 replica. From MySQL 8.0.23, ...