CREATE OR REPLACE TABLE
(MDEV-5491)
|
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 10.0.10 |
| Type: | Technical task | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Michael Widenius |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Description |
|
If CREATE OR REPLACE fails on CREATE stage, the table is still dropped, but nothing is written to the binlog. Obviously, it will cause further inconsistencies between master and slave, or upon restoring from binlog.
Test case that shows the consequent replication failure:
|
| Comments |
| Comment by Michael Widenius [ 2014-02-06 ] |
|
This is fixed by writing the failing create table select followed by rollback to the log. This should be good enough for gamma. The one disadvantage of this approach is that in case of row based logging and I plan to fix this by for this case write DROP TABLE IF EXISTS xxx to the binary log. |
| Comment by Michael Widenius [ 2014-03-20 ] |
|
Fixed and pushed into 10.0 |