- Documentation Library
- Table of Contents
- MySQL 6.0 Reference Manual
- MySQL 5.1 Reference Manual
- MySQL 5.0 Reference Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
Additional languages
MySQL 5.0 Reference Manual :: 18 Replication :: 18.3 Replication Notes and Tips :: 18.3.1 Replication Features and Issues :: 18.3.1.11 Replication and the Query Optimizer
Section Navigation [Toggle]
- 18.3.1 Replication Features and Issues
- 18.3.1.1 Replication and AUTO_INCREMENT
- 18.3.1.2 Replication and Character Sets
- 18.3.1.3 Replication DIRECTORY Statements
- 18.3.1.4 Replication with Floating-Point Values
- 18.3.1.5 Replication and FLUSH
- 18.3.1.6 Replication and Functions
- 18.3.1.7 Replication and LOAD ... Operations
- 18.3.1.8 Replication During a Master Crash
- 18.3.1.9 Replication During a Master Shutdown
- 18.3.1.10 Replication with MEMORY Tables
- 18.3.1.11 Replication and the Query Optimizer
- 18.3.1.12 Replication and Reserved Words
- 18.3.1.13 Slave Errors during Replication
- 18.3.1.14 Replication during a Slave Shutdown
- 18.3.1.15 Replication and Temporary Tables
- 18.3.1.16 Replication Retries and Timeouts
- 18.3.1.17 Replication and Time Zones
- 18.3.1.18 Replication and Transactions
- 18.3.1.19 Replication and Triggers
- 18.3.1.20 Replication and User Privileges
- 18.3.1.21 Replication and Variables
- 18.3.1.22 Replication and Views
It is possible for the data on the master and slave to become different if a statement is designed in such a way that the data modification is non-deterministic; that is, left to the will of the query optimizer. (This is in general not a good practice, even outside of replication.) For a detailed explanation of this issue, see Section B.1.8.1, “Open Issues in MySQL”.
© 1995-2008 MySQL AB. All rights reserved.
User Comments
Add your own comment.