- 4.1.1 Replication and AUTO_INCREMENT
- 4.1.2 Replication and BLACKHOLE Tables
- 4.1.3 Replication and Character Sets
- 4.1.4 Replication and CHECKSUM TABLE
- 4.1.5 Replication of CREATE SERVER, ALTER SERVER, and DROP SERVER
- 4.1.6 Replication of CREATE ... IF NOT EXISTS Statements
- 4.1.7 Replication of CREATE TABLE ... SELECT Statements
- 4.1.8 Replication of CURRENT_USER()
- 4.1.9 Replication with Differing Table Definitions on Master and Slave
- 4.1.10 Replication and DIRECTORY Table Options
- 4.1.11 Replication of DROP ... IF EXISTS Statements
- 4.1.12 Replication and Floating-Point Values
- 4.1.13 Replication and FLUSH
- 4.1.14 Replication and Fractional Seconds Support
- 4.1.15 Replication and System Functions
- 4.1.16 Replication of Invoked Features
- 4.1.17 Replication and LIMIT
- 4.1.18 Replication and LOAD DATA
- 4.1.19 Replication and max_allowed_packet
- 4.1.20 Replication and MEMORY Tables
- 4.1.21 Replication of the mysql System Database
- 4.1.22 Replication and the Query Optimizer
- 4.1.23 Replication and Partitioning
- 4.1.24 Replication and REPAIR TABLE
- 4.1.25 Replication and Reserved Words
- 4.1.26 Replication and Master or Slave Shutdowns
- 4.1.27 Slave Errors During Replication
- 4.1.28 Replication and Server SQL Mode
- 4.1.29 Replication and Temporary Tables
- 4.1.30 Replication Retries and Timeouts
- 4.1.31 Replication and Time Zones
- 4.1.32 Replication and Transactions
- 4.1.33 Replication and Triggers
- 4.1.34 Replication and TRUNCATE TABLE
- 4.1.35 Replication and Variables
- 4.1.36 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 Binary Logging of Stored Programs. For more information about row-based logging and row-based replication, see Binary Logging Formats, and Section 2.2, “Replication Formats”.