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/replica-io-thread-states.html
The following list shows the most common states you see in the State column for a replication I/O (receiver) thread on a replica server. This state also appears in the Replica_IO_State column displayed by SHOW REPLICA STATUS (or before MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/replica-logs-relaylog.html
The relay log, like the binary log, consists of a set of numbered files containing events that describe database changes, and an index file that contains the names of all used relay log files. The default location for relay log files is the data ...
https://dev.mysql.com/doc/refman/8.0/en/replica-logs-status.html
A replica server creates two replication metadata repositories, the connection metadata repository and the applier metadata repository. If binary log file position based replication is in use, when the replica restarts, it reads the two ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption-key-rotation.html
When binary log encryption is enabled, you can rotate the binary log master key at any time while the server is running by issuing ALTER INSTANCE ROTATE BINLOG MASTER KEY. You can rotate the binary log master key on a regular basis to comply with ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption-scope.html
Existing binary log files and relay log files that were present on the server when you started encryption are not encrypted. You can purge these files when they are no longer needed. Data in motion in the replication event stream, which is sent to ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption.html
From MySQL 8.0.14, binary log files and relay log files can be encrypted, helping to protect these files and the potentially sensitive data contained in them from being misused by outside attackers, and also from unauthorized viewing by users of ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-differing-tables.html
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 of the table. In addition, corresponding table columns on the source and the replica can use ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-memory.html
When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect to replicas, the first time that the source uses a given MEMORY table after startup, it logs an event that notifies replicas that the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-transaction-inconsistencies.html
Inconsistencies in the sequence of transactions that have been executed from the relay log can occur depending on your replication configuration. This section explains how to avoid inconsistencies and solve any problems they cause. A transaction ...
https://dev.mysql.com/doc/refman/8.0/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 ...