| Bug #75683 | create table db.table like tmptable is binlogged incorrectly - breaks a slave | ||
|---|---|---|---|
| Submitted: | 29 Jan 2015 18:40 | Modified: | 26 Mar 2015 13:17 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Utilities: Binlog Events | Severity: | S1 (Critical) |
| Version: | 5.1.73, 5.5.42, 5.6.22, 5.7.6 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[29 Jan 2015 18:40]
Shane Bester
[26 Mar 2015 13:17]
Erlend Dahl
Fixed in 5.5.44 5.6.25 5.7.8 5.8.0
[23 Jun 2015 13:51]
Laurynas Biveinis
commit 151b8ec4d11abbb3bf1fb55e10df3e3e7449fe1c
Author: Venkatesh Duggirala <venkatesh.duggirala@oracle.com>
Date: Fri Mar 13 12:32:44 2015 +0530
Bug #20439913 CREATE TABLE DB.TABLE LIKE TMPTABLE IS BINLOGGED INCORRECTLY - BREAKS A SLAVE
Analysis:
In row based replication, Master does not send temp table information
to Slave. If there are any DDLs that involves in regular table that needs
to be sent to Slave and a temp tables (which will not be available at Slave),
the Master rewrites the query replacing temp table with it's defintion.
Eg: create table regular_table like temptable.
In rewrite logic, server is ignoring the database of regular table
which can cause problems mentioned in this bug.
Fix: dont ignore database information (if available) while
rewriting the query
commit 59142d9a279339f766a23e35a0f7b183406e43c0
Author: Venkatesh Duggirala <venkatesh.duggirala@oracle.com>
Date: Fri Mar 13 13:13:48 2015 +0530
Bug #20439913 CREATE TABLE DB.TABLE LIKE TMPTABLE IS
BINLOGGED INCORRECTLY - BREAKS A SLAVE
Submitted a incomplete patch with my previous push,
re submitting the extra changes the required to make
the patch complete.
