Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3(EOL)
-
None
Description
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/20670
10.3 162f475c4be81dfbceed093ad03d114b |
versioning.update 'innodb,trx_id' w3 [ fail ]
|
Test ended at 2019-11-01 05:24:09
|
|
CURRENT_TEST: versioning.update
|
mysqltest: At line 174: query 'update t1 set a = 'bar'' succeeded - should have failed with errno 1213...
|
|
The result from queries just before the failure was:
|
< snip >
|
### Issue tempesta-tech/mariadb#365, bug 7 (duplicate of historical row)
|
create or replace table t1 (a int primary key, b int)
|
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
|
#
|
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
- relates to
-
MDEV-22475 versioning.update failed in buildbot with wrong result code again
- Closed