PDF (US Ltr)
- 41.9Mb
PDF (A4)
- 42.0Mb
Man Pages (TGZ)
- 272.3Kb
Man Pages (Zip)
- 378.3Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/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/9.7/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/9.7/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/9.7/en/replication-binlog-encryption.html
MySQL 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 the operating ...
https://dev.mysql.com/doc/refman/9.7/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/9.7/en/replication-features-foreign-keys.html
For InnoDB tables, foreign keys can be handled by the server runtime or by the native InnoDB implementation, depending on the innodb_native_foreign_keys system variable. Replication preserves the source's foreign keys as described in this section.
https://dev.mysql.com/doc/refman/9.7/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/9.7/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/9.7/en/replication-functions-synchronization.html
The functions listed in this section are used for controlling position-based synchronization of source and replica servers in MySQL Replication. Table 14.28 Positional Synchronization Functions Name Description Deprecated MASTER_POS_WAIT() Block ...
https://dev.mysql.com/doc/refman/9.7/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 ...