Debian Codegraph @

mysql-test/suite/binlog_gtid/r/binlog_gtid_select_taking_write_locks.result

raw
1 CREATE TABLE t1(c1 INT) ENGINE=InnoDB;
2 CREATE TABLE t2(c1 INT) ENGINE=MEMORY;
3 # TC.1 `GTID_NEXT` = `UNDEFINED` + Query statement acquiring wr-lock
4 # ------------------------------------------------------------------
5 SET GTID_NEXT='aaaaaaaa-aaaa-aaaa-aaaa-bbbbbbbbbbbb:1';
6 CREATE TABLE t3(c1 CHAR CHARACTER SET utf16) ENGINE=InnoDB;
7 SELECT * FROM t1, t2, t3 FOR UPDATE OF t1, t2, t3 SKIP LOCKED;
8 ERROR HY000: When @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is 'aaaaaaaa-aaaa-aaaa-aaaa-bbbbbbbbbbbb:1'.
9 # TC.2 `GTID_NEXT` = `ASSIGNED` + Query statement acquiring wr-lock
10 # -----------------------------------------------------------------
11 SET GTID_NEXT='aaaaaaaa-aaaa-aaaa-aaaa-bbbbbbbbbbbb:2';
12 SELECT * FROM t1, t3 FOR UPDATE OF t1, t3 SKIP LOCKED;
13 c1 c1
14 include/assert.inc [No change in `GTID_EXECUTED`]
15 include/assert.inc [No change in `GTID_OWNED`]
16 include/assert.inc [No change in `GTID_NEXT`]
17 SET GTID_NEXT='AUTOMATIC';
18 ERROR HY000: @@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns aaaaaaaa-aaaa-aaaa-aaaa-bbbbbbbbbbbb:2. Ownership is released on COMMIT or ROLLBACK.
19 COMMIT;
20 # TC.3 `GTID_NEXT` = `AUTOMATIC` + Query statement acquiring wr-lock
21 # ------------------------------------------------------------------
22 SET GTID_NEXT='AUTOMATIC';
23 CREATE TABLE t4(c1 FLOAT) ENGINE=InnoDB;
24 SELECT * FROM t1, t3, t4 FOR UPDATE OF t1, t3, t4 SKIP LOCKED;
25 c1 c1 c1
26 include/assert.inc [No change in `GTID_EXECUTED`]
27 include/assert.inc [No change in `GTID_OWNED`]
28 DROP TABLE t1;
29 DROP TABLE t2;
30 DROP TABLE t3;
31 DROP TABLE t4;
32 RESET MASTER;