File: xa_prepare_reset_supremum_lock.test

package info (click to toggle)
mariadb-10.5 1%3A10.5.23-0%2Bdeb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 712,240 kB
  • sloc: ansic: 2,158,658; cpp: 1,843,101; asm: 297,745; perl: 59,967; sh: 53,869; pascal: 38,348; java: 33,919; yacc: 19,639; python: 11,119; xml: 10,126; sql: 10,027; ruby: 8,544; makefile: 6,343; cs: 2,866; lex: 1,205; javascript: 1,037; objc: 80; tcl: 73; awk: 46; php: 22; sed: 16
file content (31 lines) | stat: -rw-r--r-- 664 bytes parent folder | download 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
 
--source include/have_innodb.inc
--source include/count_sessions.inc

CREATE TABLE t (
  `a` INT NOT NULL,
  PRIMARY KEY (`a`)
) ENGINE=InnoDB;


INSERT INTO t VALUES(10);
INSERT INTO t VALUES(20);

SET TRANSACTION ISOLATION LEVEL REPEATABLE READ;
XA START '1';
SELECT * FROM t WHERE a > 20 FOR UPDATE;
INSERT INTO t VALUES(40);
XA END '1';
XA PREPARE '1';

connect (con1,localhost,root);
SET innodb_lock_wait_timeout=1;
# This will be finished with lock wait timeout error if XA PREPARE did not
# reset lock on supremum
INSERT INTO t VALUES(50);
--disconnect con1

--connection default
XA COMMIT '1';
DROP TABLE t;

--source include/wait_until_count_sessions.inc