- 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
- 14 Replication
- 14.1 Introduction to Replication
- 14.2 Replication Implementation Overview
- 14.3 Replication Implementation Details
- 14.4 How to Set Up Replication
- 14.5 Replication Compatibility Between MySQL Versions
- 14.6 Upgrading a Replication Setup
- 14.7 Replication Features and Known Problems
- 14.8 Replication Startup Options
- 14.9 How Servers Evaluate Replication Rules
- 14.10 Replication FAQ
- 14.11 Troubleshooting Replication
- 14.12 How to Report Replication Bugs or Problems
The original binary log format was developed in MySQL 3.23. It was changed in MySQL 4.0.
Note
You cannot replicate from a master that uses a newer binary log format to a slave that uses an older format (for example, from MySQL 4.1 to MySQL 3.23.) This has significant consequences for upgrading servers in a replication setup, as described in Section 14.6, “Upgrading a Replication Setup”.
As far as replication is concerned, the binary log format for any MySQL 4.1.x version and any 4.0.x version is identical. However, replication from a 4.1 master to a 4.0 slave is unsupported, has not been tested thoroughly, and no further development or bug fixing is planned for this master/slave combination. Although the binary log format is the same for 4.0 and 4.1, there are other constraints, such as SQL-level compatibility issues. For example, a 4.1 master cannot replicate to a 4.0 slave if the replicated statements use SQL features available in 4.1 but not 4.0. In addition, there are known issues with trying to replicate from a 4.0 master to a 5.1 slave (Bug#31240). These and other issues are discussed in Section 14.7, “Replication Features and Known Problems”.
As a general rule, we recommended using recent MySQL versions, because replication capabilities are continually being improved. We also recommend using the same version for both the master and the slave. We recommend upgrading masters and slaves running alpha or beta versions to new versions.
User Comments
Please read carefully the paragraph about new password algorithm in chapter "Replication Features and Known Problems" - this leads also to problems with the "replication user" while setting up Master with version 4.1.x and Slave with version 4.0.x - solutions can be found at section "A.2.3 Client does not support authentication protocol".
Add your own comment.