MySQL 5.7 Release Notes
- 16.4.1.1 Replication and AUTO_INCREMENT
- 16.4.1.2 Replication and BLACKHOLE Tables
- 16.4.1.3 Replication and Character Sets
- 16.4.1.4 Replication and CHECKSUM TABLE
- 16.4.1.5 Replication of CREATE ... IF NOT EXISTS Statements
- 16.4.1.6 Replication of CREATE TABLE ... SELECT Statements
- 16.4.1.7 Replication of CREATE SERVER, ALTER SERVER, and DROP SERVER
- 16.4.1.8 Replication of CURRENT_USER()
- 16.4.1.9 Replication of DROP ... IF EXISTS Statements
- 16.4.1.10 Replication with Differing Table Definitions on Source and Replica
- 16.4.1.11 Replication and DIRECTORY Table Options
- 16.4.1.12 Replication and Floating-Point Values
- 16.4.1.13 Replication and Fractional Seconds Support
- 16.4.1.14 Replication and FLUSH
- 16.4.1.15 Replication and System Functions
- 16.4.1.16 Replication of Invoked Features
- 16.4.1.17 Replication and LIMIT
- 16.4.1.18 Replication and LOAD DATA
- 16.4.1.19 Replication and max_allowed_packet
- 16.4.1.20 Replication and MEMORY Tables
- 16.4.1.21 Replication of the mysql System Database
- 16.4.1.22 Replication and the Query Optimizer
- 16.4.1.23 Replication and Partitioning
- 16.4.1.24 Replication and REPAIR TABLE
- 16.4.1.25 Replication and Reserved Words
- 16.4.1.26 Replication and Source or Replica Shutdowns
- 16.4.1.27 Replica Errors During Replication
- 16.4.1.28 Replication and Server SQL Mode
- 16.4.1.29 Replication and Temporary Tables
- 16.4.1.30 Replication Retries and Timeouts
- 16.4.1.31 Replication and Time Zones
- 16.4.1.32 Replication and Transaction Inconsistencies
- 16.4.1.33 Replication and Transactions
- 16.4.1.34 Replication and Triggers
- 16.4.1.35 Replication and TRUNCATE TABLE
- 16.4.1.36 Replication and User Name Length
- 16.4.1.37 Replication and Variables
- 16.4.1.38 Replication and Views
The following sections provide information about what is supported and what is not in MySQL replication, and about specific issues and situations that may occur when replicating certain statements.
Statement-based replication depends on compatibility at the SQL level between the source and replica. In other words, successful statement-based replication requires that any SQL features used be supported by both the source and the replica servers. If you use a feature on the source server that is available only in the current version of MySQL, you cannot replicate to a replica that uses an earlier version of MySQL. Such incompatibilities can also occur within a release series as well as between versions.
If you are planning to use statement-based replication between MySQL 5.7 and a previous MySQL release series, it is a good idea to consult the edition of the MySQL Reference Manual corresponding to the earlier release series for information regarding the replication characteristics of that series.
With MySQL's statement-based replication, there may be issues with replicating stored routines or triggers. You can avoid these issues by using MySQL's row-based replication instead. For a detailed list of issues, see Section 23.7, “Stored Program Binary Logging”. For more information about row-based logging and row-based replication, see Section 5.4.4.1, “Binary Logging Formats”, and Section 16.2.1, “Replication Formats”.
For additional information specific to replication and
InnoDB, see
Section 14.20, “InnoDB and MySQL Replication”. For information
relating to replication with NDB Cluster, see
Section 21.7, “NDB Cluster Replication”.