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-channels.html
Channel specific replication filters can be used when the same database or table is present on multiple sources, and you only need the replica to replicate it from one source. In MySQL multi-source replication, a replica opens multiple replication ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-mysqldb.html
Data modification statements made to tables in the mysql schema are replicated according to the value of binlog_format; if this value is MIXED, these statements are replicated using row-based format. However, statements that would normally update ...
https://dev.mysql.com/doc/refman/8.0/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. It blocks until the replica has read and applied all updates up to the specified position in the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-functions.html
The functions described in the following sections are used with MySQL Replication. GTID_SUBTRACT() Return all GTIDs in set that are not in subset. MASTER_POS_WAIT() Block until the replica has read and applied all updates up to the specified ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-assign-anon.html
The Performance Schema replication_applier_configuration table shows whether GTIDs are assigned to anonymous transactions on a replication channel, what the UUID is, and whether it is the UUID of the replica server (LOCAL) or a user-specified UUID ... From MySQL 8.0.23, you can set up replication channels to assign a GTID to replicated transactions that do not already have ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-auto-positioning.html
The alternative SOURCE_LOG_FILE | MASTER_LOG_FILE and SOURCE_LOG_POS | MASTER_LOG_POS options specify the name of the log file and the starting position within the file, but with GTIDs the replica does not need this nonlocal data.. This GTID set is ... GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-failover.html
This method is simple and effective, but requires the replica to read the binary log from the source; it can sometimes take a comparatively long time for the new replica to catch up with the source, so this method is not suitable for fast failover ... There are a number of techniques when using MySQL Replication with Global Transaction Identifiers (GTIDs) for provisioning a new replica which can then be used for scaleout, being promoted to source as necessary for ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-functions.html
The function can return the union of gtid_executed on each replica with the set of transactions received by the replica, which is recorded in the Performance Schema replication_connection_status table. This section provides examples of stored ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-howto.html
It is not mandatory to have binary logging enabled in order to use GTIDs when using the mysql.gtid_executed Table. This section describes a process for configuring and starting GTID-based replication in MySQL 8.0. This is a “cold start” ...
https://dev.mysql.com/doc/refman/8.0/en/replication-implementation.html
Tables are created or their structure modified, and data is inserted, deleted, and updated according to the changes that were originally made on the source. Replication is based on the source server keeping track of all changes to its databases ...