- 188.8.131.52 Replication and AUTO_INCREMENT
- 184.108.40.206 Replication and BLACKHOLE Tables
- 220.127.116.11 Replication and Character Sets
- 18.104.22.168 Replication and CHECKSUM TABLE
- 22.214.171.124 Replication of CREATE SERVER, ALTER SERVER, and DROP SERVER
- 126.96.36.199 Replication of CREATE ... IF NOT EXISTS Statements
- 188.8.131.52 Replication of CREATE TABLE ... SELECT Statements
- 184.108.40.206 Replication of CURRENT_USER()
- 220.127.116.11 Replication with Differing Table Definitions on Master and Slave
- 18.104.22.168 Replication and DIRECTORY Table Options
- 22.214.171.124 Replication of DROP ... IF EXISTS Statements
- 126.96.36.199 Replication and Floating-Point Values
- 188.8.131.52 Replication and FLUSH
- 184.108.40.206 Replication and Fractional Seconds Support
- 220.127.116.11 Replication and System Functions
- 18.104.22.168 Replication of Invoked Features
- 22.214.171.124 Replication and LIMIT
- 126.96.36.199 Replication and LOAD DATA
- 188.8.131.52 Replication and max_allowed_packet
- 184.108.40.206 Replication and MEMORY Tables
- 220.127.116.11 Replication of the mysql System Database
- 18.104.22.168 Replication and the Query Optimizer
- 22.214.171.124 Replication and Partitioning
- 126.96.36.199 Replication and REPAIR TABLE
- 188.8.131.52 Replication and Reserved Words
- 184.108.40.206 Replication and Master or Slave Shutdowns
- 220.127.116.11 Slave Errors During Replication
- 18.104.22.168 Replication and Server SQL Mode
- 22.214.171.124 Replication and Temporary Tables
- 126.96.36.199 Replication Retries and Timeouts
- 188.8.131.52 Replication and Time Zones
- 184.108.40.206 Replication and Transactions
- 220.127.116.11 Replication and Triggers
- 18.104.22.168 Replication and TRUNCATE TABLE
- 22.214.171.124 Replication and Variables
- 126.96.36.199 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 master and slave. In other words, successful SBR requires that any SQL features used be supported by both the master and the slave servers. For example, if you use a feature on the master server that exists in MySQL 5.6 but was removed in MySQL 5.7, errors will occur if you replicate to a slave that uses MySQL 5.7. Such incompatibilities also can occur within a release series when using pre-production releases of MySQL.
For this reason, use Generally Available (GA) releases of MySQL for statement-based replication in a production setting, since we do not introduce new SQL statements or change their behavior within a given release series once that series reaches GA release status.
If you are planning to use statement-based replication between MySQL 5.6 and a previous MySQL release series, it is also 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 20.7, “Stored Program Binary Logging”. For more information about row-based logging and row-based replication, see Section 188.8.131.52, “Binary Logging Formats”, and Section 17.1.2, “Replication Formats”.
For additional information specific to replication and
Section 14.19, “InnoDB and MySQL Replication”. For information
relating to replication with NDB Cluster, see
Section 18.6, “NDB Cluster Replication”.