Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.1, 10.2
-
None
Description
MDEV-7861 says it was pushed to 10.2, but according to git history, it only made it to 10.3. So, the test still fails the same way in 10.1-10.2. The fix should be backported at least to 10.2, and maybe in 10.1 if it's still alive by then.
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/23928
main.innodb_mysql_lock 'xtradb' w2 [ fail ]
|
Test ended at 2020-06-07 08:43:06
|
|
|
CURRENT_TEST: main.innodb_mysql_lock
|
mysqltest: At line 55: query 'INSERT INTO t1 VALUES (2)' succeeded - should have failed with errno 1213...
|
|
|
The result from queries just before the failure was:
|
< snip >
|
#
|
# Bug #22876 Four-way deadlock
|
#
|
DROP TABLE IF EXISTS t1;
|
# Connection 1
|
set @@autocommit=0;
|
CREATE TABLE t1(s1 INT UNIQUE) ENGINE=innodb;
|
INSERT INTO t1 VALUES (1);
|
# Connection 2
|
set @@autocommit=0;
|
INSERT INTO t1 VALUES (2);
|
INSERT INTO t1 VALUES (1);
|
# Connection 3
|
set @@autocommit=0;
|
DROP TABLE t1;
|
# Connection 1
|
# 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.
|
INSERT INTO t1 VALUES (2);
|
Attachments
Issue Links
- relates to
-
-
- Closed
-