Debian Codegraph @

mysql-test/suite/binlog_nogtid/r/binlog_nogtid_select_taking_write_locks.result

raw
1 include/rpl_set_gtid_mode.inc [OFF_PERMISSIVE on servers 1]
2 CREATE TABLE t1(c1 INT) ENGINE=InnoDB;
3 CREATE TABLE t2(c1 INT) ENGINE=MEMORY;
4 # TC.1 `GTID_NEXT` = `UNDEFINED` + Query statement acquiring wr-lock
5 # ------------------------------------------------------------------
6 SET GTID_NEXT='aaaaaaaa-aaaa-aaaa-aaaa-bbbbbbbbbbbb:1';
7 CREATE TABLE t3(c1 CHAR CHARACTER SET utf16) ENGINE=InnoDB;
8 SELECT * FROM t1, t2, t3 FOR UPDATE OF t1, t2, t3 SKIP LOCKED;
9 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'.
10 # TC.2 `GTID_NEXT` = `ASSIGNED` + Query statement acquiring wr-lock
11 # -----------------------------------------------------------------
12 SET GTID_NEXT='aaaaaaaa-aaaa-aaaa-aaaa-bbbbbbbbbbbb:2';
13 SELECT * FROM t1, t3 FOR UPDATE OF t1, t3 SKIP LOCKED;
14 c1 c1
15 include/assert.inc [No change in `GTID_EXECUTED`]
16 include/assert.inc [No change in `GTID_OWNED`]
17 include/assert.inc [No change in `GTID_NEXT`]
18 SET GTID_NEXT='AUTOMATIC';
19 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.
20 COMMIT;
21 # TC.3 `GTID_NEXT` = `AUTOMATIC` + Query statement acquiring wr-lock
22 # ------------------------------------------------------------------
23 SET GTID_NEXT='AUTOMATIC';
24 CREATE TABLE t4(c1 FLOAT) ENGINE=InnoDB;
25 SELECT * FROM t1, t3, t4 FOR UPDATE OF t1, t3, t4 SKIP LOCKED;
26 c1 c1 c1
27 include/assert.inc [No change in `GTID_EXECUTED`]
28 include/assert.inc [No change in `GTID_OWNED`]
29 DROP TABLE t1;
30 DROP TABLE t2;
31 DROP TABLE t3;
32 DROP TABLE t4;
33 RESET MASTER;
34 include/rpl_set_gtid_mode.inc