Debian Codegraph @

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

raw
1 call mtr.add_suppression("Found 1 prepared XA transactions");
2 RESET MASTER;
3 CREATE TABLE t1 (a INT) ENGINE=InnoDB;
4 FLUSH LOGS;
5 #
6 # Verify that selecting from mysql.gtid_executed table
7 # explicitly by a XA transaction does not cause an error.
8 #
9 XA START '1';
10 INSERT INTO t1 VALUES(1);
11 INSERT INTO t1 VALUES(2);
12 SELECT * FROM mysql.gtid_executed;
13 source_uuid interval_start interval_end
14 MASTER_UUID 1 1
15 XA END '1';
16 XA PREPARE '1';
17 #
18 # Crash the server after preparing a XA transaction
19 # and right before committing the XA transaction
20 #
21 include/execute_to_conditional_timestamp_sync_point.inc [before_commit_xa_trx]
22 XA COMMIT '1';
23 # Kill the server
24 #
25 # Verify that the following recovery is not aborting due to an
26 # innodb_lock_wait_timeout error when it is reading the system
27 # gtid_executed table.
28 #
29 # restart
30 # Rollback the XA transaction with xid '1' in order to release
31 # MDL lock for the table t1 and so allow the statement DROP TABLE t1
32 # to be executed successfully.
33 XA ROLLBACK '1';
34 DROP TABLE t1;