File: galera_toi_lock_exclusive.test

package info (click to toggle)
mariadb-10.1 10.1.45-0%2Bdeb9u1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 476,916 kB
  • sloc: cpp: 1,124,656; ansic: 871,843; perl: 52,917; sh: 40,078; pascal: 35,370; javascript: 15,555; yacc: 14,728; ruby: 8,684; xml: 5,377; sql: 3,490; makefile: 2,934; python: 1,970; java: 1,691; asm: 837; lex: 757; php: 22; sed: 16
file content (38 lines) | stat: -rw-r--r-- 1,032 bytes parent folder | download | duplicates (7)
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
32
33
34
35
36
37
38
--source include/galera_cluster.inc
--source include/have_innodb.inc

#
# Ensure that ALTER LOCK=EXCLUSIVE works under TOI. It is difficult to check that concurrent operations 
# are truly not possible, but at least we expect no hangs or deadlocks
#

CREATE TABLE t1 (id INT PRIMARY KEY) ENGINE=InnoDB;
INSERT INTO t1 VALUES (1);

# Start a transaction that is concurrent to the DDL. This is not strictly necessary for this test
# but does put more locks into play.
--connection node_2
SET AUTOCOMMIT=OFF;
START TRANSACTION;
INSERT INTO t1 VALUES (2);

--let $galera_connection_name = node_2a
--let $galera_server_number = 2
--source include/galera_connect.inc
--connection node_2a
ALTER TABLE t1 ADD COLUMN f2 INTEGER, LOCK=EXCLUSIVE;

# In Galera, a concurrent transaction aborts in the face of ALTER
--connection node_2
--error ER_LOCK_DEADLOCK
COMMIT;

--connection node_1
INSERT INTO t1 VALUES (2, 2);
SELECT COUNT(*) = 2 FROM t1;

--connection node_2
INSERT INTO t1 VALUES (3, 3);
SELECT COUNT(*) = 3 FROM t1;

DROP TABLE t1;