Bug #2428 | --old-rpl-compat is broken | ||
---|---|---|---|
Submitted: | 16 Jan 2004 9:23 | Modified: | 18 Jan 2004 8:40 |
Reporter: | Masaki Fujimoto | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 4.0.17 | OS: | Linux (Debian GNU Linux (Woody)) |
Assigned to: | Guilhem Bichot | CPU Architecture: | Any |
[16 Jan 2004 9:23]
Masaki Fujimoto
[18 Jan 2004 8:40]
Guilhem Bichot
This option, --old-rpl-compat, was introduced in MySQL 4.0.0-alpha (released in 2001), which was a very early development release of 4.0, which replication has little to do with the current one in MySQL 4.0.17. Simply put, this option should have been removed since a long time; it produces nothing usable: it produces binary logs events in a format which is a mixture of the format of 3.23 and the format of 4.0, so which is readable by no version :( Moreover, this option, even if it worked, would be of no use, as MySQL 3.23 can't be a slave of a MySQL 4.0 master (so there is no point in making a 4.0 produce binary logs in the format of 3.23). This out-of-date option should never have slipped into the production releases of MySQL 4.0; I will immediately remove it from MySQL 4.0.18. Please accept all our excuses, and thank you for pointing us to this. Regards, Guilhem