PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.3Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/replication-features-fractional-seconds.html
There may be problems replicating from a source server that understands fractional seconds to an older replica (MySQL 5.6.3 and earlier) that does not: For CREATE TABLE statements containing columns that have an fsp (fractional seconds precision) ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-mysqldb.html
Data modification statements made to tables in the mysql database 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/5.7/en/replication-gtids-auto-positioning.html
This GTID set is equal to the union of the set of GTIDs in the gtid_executed system variable (@@GLOBAL.gtid_executed), and the set of GTIDs recorded in the Performance Schema replication_connection_status table as received transactions (the result ... 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/5.7/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/5.7/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/5.7/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 5.7. This is a “cold start” ...
https://dev.mysql.com/doc/refman/5.7/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 replication source server keeping track of all changes to its ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source-adding-binlog-master.html
These steps assume that you have enabled binary logging on the replication source server using --log-bin, the replica is using TABLE based replication metadata repositories, and that you have enabled a replication user and noted the current binary ...Use the CHANGE MASTER TO statement to configure a replication channel for each source on the replica (see Section 16.2.2, “Replication ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source-adding-gtid-master.html
These steps assume you have enabled GTIDs for transactions on the replication source servers using gtid_mode=ON, created a replication user, ensured that the replica is using TABLE based replication metadata repositories, and provisioned the ...Use ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source.html
MySQL multi-source replication enables a replica to receive transactions from multiple immediate sources in parallel. In a multi-source replication topology, a replica creates a replication channel for each source that it should receive ...