Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
10.3(EOL)
Description
MDEV-20955 has been closed for a long time, the failure suddenly reappeared in 10.3 on 2020-04-29.
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-jessie-amd64/builds/8827
10.3 1fbdcada73c1861b85080eede9514029 |
versioning.update 'innodb,trx_id' w4 [ fail ]
|
Test ended at 2020-04-29 03:02:49
|
|
CURRENT_TEST: versioning.update
|
mysqltest: At line 175: query 'update t1 set a = 'bar'' succeeded - should have failed with errno 1213...
|
|
The result from queries just before the failure was:
|
< snip >
|
with system versioning engine myisam;
|
insert into t1 (a) values (1);
|
replace t1 values (1,2),(1,3),(2,4);
|
#
|
# MDEV-14829 Assertion `0' failed in Protocol::end_statement upon concurrent UPDATE
|
#
|
set @old_lock_wait_timeout= @@innodb_lock_wait_timeout;
|
set @@innodb_lock_wait_timeout= 1073741824;
|
create or replace table t1 (pk int, a char(3), b char(3), primary key(pk))
|
engine=innodb with system versioning;
|
insert into t1 (pk) values (1);
|
connect con1,localhost,root,,test;
|
start transaction;
|
select * from t1 for update;
|
pk a b
|
1 NULL NULL
|
connection default;
|
update t1 set b = 'foo';
|
connection con1;
|
update t1 set a = 'bar';
|
Attachments
Issue Links
- is part of
-
MDEV-18706 ER_LOCK_DEADLOCK on concurrent read and insert into already locked gap
- In Review
- relates to
-
MDEV-16226 TRX_ID-based System Versioning refactoring
- Stalled
-
MDEV-20955 versioning.update failed in buildbot with wrong result code
- Closed