Search Results
https://dev.mysql.com/doc/refman/8.4/en/replication-encrypted-connections.html
To use an encrypted connection for the transfer of the binary log required during replication, both the source and the replica servers must support encrypted network connections. If either server does not support encrypted connections (because it ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-auto-increment.html
Statement-based replication of AUTO_INCREMENT, LAST_INSERT_ID(), and TIMESTAMP values is carried out subject to the following exceptions: A statement invoking a trigger or function that causes an update to an AUTO_INCREMENT column is not replicated ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-limit.html
Statement-based replication of LIMIT clauses in DELETE, UPDATE, and INSERT ... SELECT statements is unsafe since the order of the rows affected is not defined. (Such statements can be replicated correctly with statement-based replication only if ...
https://dev.mysql.com/doc/refman/8.4/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.4/en/replication-gtids-auto-positioning.html
GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and replica. When GTIDs are in use, all the information that the replica needs for synchronizing with ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-concepts.html
A global transaction identifier (GTID) is a unique identifier created and associated with each transaction committed on the server of origin (the source). This identifier is unique not only to the server on which it originated, but is unique across ...
https://dev.mysql.com/doc/refman/8.4/en/replication-howto-masterbaseconfig.html
To configure a source to use binary log file position based replication, you must ensure that binary logging is enabled, and establish a unique server ID. Each server within a replication topology must be configured with a unique server ID, which ...
https://dev.mysql.com/doc/refman/8.4/en/replication-howto.html
This section describes how to set up a MySQL server to use binary log file position based replication. There are a number of different methods for setting up replication, and the exact method to use depends on how you are setting up replication, ...
https://dev.mysql.com/doc/refman/8.4/en/replication-implementation.html
Replication is based on the source server keeping track of all changes to its databases (updates, deletes, and so on) in its binary log. The binary log serves as a written record of all events that modify database structure or content (data) from ...
https://dev.mysql.com/doc/refman/8.4/en/replication-mode-change-online-disable-gtids.html
This section describes how to disable GTID transactions on servers that are already online. This procedure does not require taking the server offline and is suited to use in production. However, if you have the possibility to take the servers ...