diff options
| author | Jon Olav Hauglid <jon.hauglid@oracle.com> | 2011-03-15 11:49:14 +0100 |
|---|---|---|
| committer | Jon Olav Hauglid <jon.hauglid@oracle.com> | 2011-03-15 11:49:14 +0100 |
| commit | f94e7288e33332584074ee85f625db9a93f2369c (patch) | |
| tree | 950a342d595c06075a38131e24eaf988f58c558a /mysys/string.c | |
| parent | dd14e37661965d9f8ec7ff7704c161bde0558dc1 (diff) | |
| download | mariadb-git-f94e7288e33332584074ee85f625db9a93f2369c.tar.gz | |
Bug #11765416 (former 58381)
FAILED DROP DATABASE CAN BREAK STATEMENT BASED REPLICATION
The first phase of DROP DATABASE is to delete the tables in the database.
If deletion of one or more of the tables fail (e.g. due to a FOREIGN KEY
constraint), DROP DATABASE will be aborted. However, some tables could
still have been deleted. The problem was that nothing would be written
to the binary log in this case, so any slaves would not delete these tables.
Therefore the master and the slaves would get out of sync.
This patch fixes the problem by making sure that DROP TABLE is written
to the binary log for the tables that were in fact deleted by the failed
DROP DATABASE statement.
Test case added to binlog.binlog_database.test.
Diffstat (limited to 'mysys/string.c')
0 files changed, 0 insertions, 0 deletions