mirror of
https://github.com/MariaDB/server.git
synced 2025-10-31 10:56:12 +01:00
49791cbc6f
This commit contains a fix, where the replication write set for a CREATE TABLE will contain, as certification keys, table names for all FK references. With this, all DML for the FK parent tables will conflict with the CREATE TABLE statement. There is also new test galera.MDEV-27276 to verify the fix. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
21 lines
825 B
Text
21 lines
825 B
Text
connection node_2;
|
|
connection node_1;
|
|
FLUSH TABLES WITH READ LOCK;
|
|
CREATE TABLE t1 (a INT) ENGINE=InnoDB;
|
|
ERROR 08S01: Aborting TOI: Replication paused on node for FTWRL/BACKUP STAGE.
|
|
SET wsrep_OSU_method=RSU;
|
|
CREATE TABLE t1 (a INT) ENGINE=InnoDB;
|
|
ERROR 08S01: Aborting TOI: Replication paused on node for FTWRL/BACKUP STAGE.
|
|
SET wsrep_OSU_method=TOI;
|
|
connect node_1a, 127.0.0.1, root, , test, $NODE_MYPORT_1;
|
|
CREATE TABLE t1 (a INT) ENGINE=InnoDB;
|
|
ERROR 08S01: Aborting TOI: Replication paused on node for FTWRL/BACKUP STAGE.
|
|
connection node_1;
|
|
UNLOCK TABLES;
|
|
CREATE TABLE t1 (a INT) ENGINE=InnoDB;
|
|
FLUSH TABLES WITH READ LOCK;
|
|
INSERT INTO t1 VALUES (1);
|
|
ERROR HY000: Can't execute the query because you have a conflicting read lock
|
|
UNLOCK TABLES;
|
|
DROP TABLE t1;
|
|
CALL mtr.add_suppression("CREATE TABLE isolation failure");
|