Bug #198 Replication between a 4.0.12 master and 3.23.52 slave does not work
| Submitted: | 27 Mar 2003 6:31 | Modified: | 21 Jun 2003 7:31 |
|---|---|---|---|
| Reporter: | Guilhem Bichot | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 3.23, 4.0 | OS: | Any (all) |
| Assigned to: | Guilhem Bichot | CPU Architecture: | Any |
[27 Mar 2003 6:31]
Guilhem Bichot
[27 Mar 2003 6:32]
Guilhem Bichot
Here the customer wants to upgrade soon to 4.0, so it is probably ok (I asked him if it was) to not fix it.
[27 Mar 2003 7:07]
Guilhem Bichot
By the way, it is documented in the manual that 3.23 cannot replicate 4.0.
[21 Jun 2003 7:31]
Guilhem Bichot
Thank you for your bug report. This issue has been fixed in the latest
development tree for that product. You can find more information about
accessing our development trees at
http://www.mysql.com/doc/en/Installing_source_tree.html
3.23.58 slaves will detect the problem and print an error.
If the master is 4.0.x with x<14, the slave may not immediately detect the problem if he has asked for a binlog position >4 (then the slave will detect the problem when the master sends the next binlog). If the master is 4.0.14 or newer, the slave will always detect the problem as soon as replication starts.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.