Bug #76493 | Binlog statement is not ignored | ||
---|---|---|---|
Submitted: | 26 Mar 2015 12:32 | Modified: | 25 Aug 2015 15:55 |
Reporter: | Dan Lukes | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 5.6.20, 5.6.23, 5.6.25 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[26 Mar 2015 12:32]
Dan Lukes
[30 Mar 2015 10:36]
MySQL Verification Team
Hello Dan Lukes, Thank you for the report and test case. Observed this behavior on 5.6.23. Thanks, Umesh
[30 Mar 2015 10:39]
MySQL Verification Team
test results
Attachment: 76493.txt (text/plain), 14.59 KiB.
[30 Mar 2015 11:12]
MySQL Verification Team
test results
Attachment: 76493_5.6.25.txt (text/plain), 13.78 KiB.
[25 Aug 2015 15:55]
David Moss
Thanks for your feedback, this has been fixed in upcoming versions and the following was noted in the 5.6.27 and 5.7.9 changelogs: If a CREATE VIEW statement failed, it was being incorrectly written to the binary log even though it did not result in the creation of a partial view. The fix ensures that such statements are not recorded in the binary log. Additionally it was found that when a statement which had failed on a master was received by a slave with an expected error, if the statement was skipped on the slave, for example due to a replication filter, the expected error was being compared with the actual error that happened on the slave. The fix ensures that if a statement with an expected error is received by a slave, if the statement has not been filtered, only then is it compared with the actual error that happened on the slave.