Debian Codegraph @

mysql-test/suite/perfschema/t/data_locks_join.test

raw
1 --echo Bug #28733170
2 --echo PERFORMANCE_SCHEMA.DATA_LOCKS DOES NOT HANDLE JOINS CORRECTLY
3
4 CREATE TABLE t1(
5 id INT PRIMARY KEY
6 ) Engine=InnoDB;
7
8 INSERT INTO t1 VALUES (1);
9 # Create a situation in which a transaction holds more than one lock on same record.
10 BEGIN;
11 SELECT * FROM t1 WHERE id=1 FOR SHARE;
12 SELECT * FROM t1 WHERE id=1 FOR UPDATE;
13
14 --connect (C1, localhost, root,,)
15 # Store all engine_lock_id-s in t2
16
17 CREATE TABLE t2 (
18 id INT PRIMARY KEY AUTO_INCREMENT,
19 lock_id VARCHAR(200) NOT NULL
20 ) Engine=InnoDB;
21
22 INSERT INTO t2 (lock_id)
23 SELECT engine_lock_id
24 FROM performance_schema.data_locks
25 WHERE object_name='t1';
26
27 # We expect the number of rows in the JOIN
28 # to be equal to the number of rows in t2.
29 # The bug was causing this JOIN to return only single row.
30
31 SELECT COUNT(*) FROM t2;
32
33 SELECT COUNT(t2.id)
34 FROM t2
35 JOIN performance_schema.data_locks dl
36 ON(dl.engine_lock_id = t2.lock_id)
37 ORDER BY t2.id;
38
39 DROP TABLE t2;
40
41 --connection default
42 ROLLBACK;
43
44 --disconnect C1
45
46 DROP TABLE t1;