Bug #69175 query caused different errors on master and slave
| Submitted: | 8 May 2013 11:08 | Modified: | 14 Sep 2013 9:23 |
|---|---|---|---|
| Reporter: | wei liu | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
| Version: | 5.5.16 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | query caused different errors on master and slave, readonly, truncate table | ||
[8 May 2013 11:08]
wei liu
[28 May 2013 7:17]
wei liu
Is there any work around to make the replication process to skip this error?
[14 Aug 2013 9:07]
wei liu
Is there any progress so far?
[14 Aug 2013 9:23]
MySQL Verification Team
Hello Wei Liu, Thank you for the report. I can not repeat described behavior with dummy data. Additionally version 5.5.16 is old and many bugs were fixed since. Please could you check in latest GA release and see if you can repeat? Please let us know if it is repeatable on 5.5.33(GA). Thanks, Umesh
[15 Sep 2013 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.054 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.