- 18.104.22.168 Replication and AUTO_INCREMENT
- 22.214.171.124 Replication and Character Sets
- 126.96.36.199 Replication and CHECKSUM TABLE
- 188.8.131.52 Replication of CREATE TABLE ... SELECT Statements
- 184.108.40.206 Replication of DROP ... IF EXISTS Statements
- 220.127.116.11 Replication and DIRECTORY Table Options
- 18.104.22.168 Replication and Floating-Point Values
- 22.214.171.124 Replication and FLUSH
- 126.96.36.199 Replication and System Functions
- 188.8.131.52 Replication and LIMIT
- 184.108.40.206 Replication and LOAD Operations
- 220.127.116.11 Replication and the Slow Query Log
- 18.104.22.168 Replication and REPAIR TABLE
- 22.214.171.124 Replication and Master or Slave Shutdowns
- 126.96.36.199 Replication and MEMORY Tables
- 188.8.131.52 Replication and Temporary Tables
- 184.108.40.206 Replication of the mysql System Database
- 220.127.116.11 Replication and User Privileges
- 18.104.22.168 Replication and the Query Optimizer
- 22.214.171.124 Replication and Reserved Words
- 126.96.36.199 Slave Errors During Replication
- 188.8.131.52 Replication and Server SQL Mode
- 184.108.40.206 Replication Retries and Timeouts
- 220.127.116.11 Replication and TIMESTAMP
- 18.104.22.168 Replication and Time Zones
- 22.214.171.124 Replication and Transactions
- 126.96.36.199 Replication and Triggers
- 188.8.131.52 Replication and Views
- 184.108.40.206 Replication and Variables
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 others, 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 is available only in MySQL 5.0 (or later), you cannot replicate to a slave that uses MySQL 4.1 (or earlier).
Such incompatibilities also can occur within a release series when
using pre-production releases of MySQL. For example, the
SLEEP() function is available
beginning with MySQL 5.0.12. If you use this function on the
master, you cannot replicate to a slave that uses MySQL 5.0.11 or
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 replication between MySQL 5.0 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.
For additional information specific to replication and
Section 220.127.116.11, “InnoDB and MySQL Replication”.