CREATE TABLE t LIKE <temporary table>
Bug #1212247 reported by
Seppo Jaakola
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Medium
|
Seppo Jaakola | |||
5.6 |
Fix Released
|
Medium
|
Seppo Jaakola | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
CREATE TABLE t LIKE tmp, where tmp is a temporary table, will cause serious problem for replication.
This create statement will be replicated as plain SQL statement, and then the create statement will not be possible to apply in slave nodes, as the temporary table is not present there. If there are later DML for this table, all other nodes will crash, as DML cannot be applied due to missing table.
Changed in codership-mysql: | |
importance: | Undecided → Medium |
assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
Changed in percona-xtradb-cluster: | |
milestone: | none → 5.5.33-23.7.6 |
Changed in codership-mysql: | |
status: | New → In Progress |
milestone: | none → 5.5.32-23.7.6 |
Changed in percona-xtradb-cluster: | |
status: | New → Fix Committed |
Changed in codership-mysql: | |
status: | Fix Committed → Fix Released |
Changed in percona-xtradb-cluster: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The fix replicates CREATE TABLE LIKE <tmp table> with two query log events:
1. first the CREATE TABLE for the source temporary table
2. then the actual CREATE TABLE LIKE... event
This way, the slave applier will get to see the definition of the temporary table. The temporary table is dropped in the slave applier at the end of processing of the replication bundle.
Fix is pushed in revision: http:// bazaar. launchpad. net/~codership/ codership- mysql/5. 5-23/revision/ 3900