1berry/MariaDB-server
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Make mysql.innodb_mysql_lock deterministic

Browse Source 
MDEV-7861 main.innodb_mysql_lock fails sporadically in buildbot
This commit is contained in:
Monty 2020-03-26 19:39:51 +02:00
parent caf110fa52
commit 0fb84216a3
2 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
mysql-test/main/innodb_mysql_lock.result
View File

@ -21,6 +21,7 @@ connection con3;
set @@autocommit=0;
DROP TABLE t1;
connection con1;
# Waiting for until transaction will be locked inside innodb subsystem
# Connection 1 is now holding the lock.
# Issuing insert from connection 1 while connection 2&3
# is waiting for the lock should give a deadlock error.

9
mysql-test/main/innodb_mysql_lock.test
View File

@ -1,3 +1,4 @@
--source include/have_metadata_lock_info.inc
-- source include/have_innodb.inc
# Save the initial number of concurrent sessions.
@ -36,10 +37,12 @@ set @@autocommit=0;
--send DROP TABLE t1
connection con1;
--echo # Waiting for until transaction will be locked inside innodb subsystem
let $wait_condition=
SELECT COUNT(*) = 1 FROM information_schema.processlist
WHERE info = "INSERT INTO t1 VALUES (1)" and
state = "update";
SELECT COUNT(*) = 1 FROM information_schema.innodb_trx
WHERE trx_query = 'INSERT INTO t1 VALUES (1)' AND
trx_operation_state = 'inserting' AND
trx_state = 'LOCK WAIT';
--source include/wait_condition.inc
let $wait_condition=
SELECT COUNT(*) = 1 FROM information_schema.processlist