mirror of
https://github.com/MariaDB/server.git
synced 2025-11-30 05:23:50 +03:00
4a872ae1e7
If, during backup 1) Innodb table is dropped (after being copied to backup) and then 2) Before backup finished, another Innodb table is renamed, and new name is the name of the dropped table in 1) then, --prepare fails with assertion, as DDL fixup code in prepare did not handle this specific case. The fix is to process drops before renames, in prepare DDL-"redo" phase.
19 lines
438 B
Plaintext
19 lines
438 B
Plaintext
CREATE TABLE t1 (i int) ENGINE=INNODB;
|
|
CREATE TABLE t2 (i int) ENGINE=INNODB;
|
|
CREATE TABLE t3 (i int) ENGINE=INNODB;
|
|
CREATE TABLE t4 (i int) ENGINE=INNODB;
|
|
CREATE TABLE t5 (i int) ENGINE=INNODB;
|
|
# xtrabackup prepare
|
|
# shutdown server
|
|
# remove datadir
|
|
# xtrabackup move back
|
|
# restart server
|
|
CREATE TABLE t1(i int);
|
|
DROP TABLE t1;
|
|
CREATE TABLE t2(i int);
|
|
DROP TABLE t2;
|
|
DROP TABLE t3;
|
|
CREATE TABLE t4(i int);
|
|
DROP TABLE t4;
|
|
DROP TABLE t5;
|