[MDEV-4044] LevelDB: UPDATE or DELETE with ORDER BY locks itself and ends with ER_LOCK_WAIT_TIMEOUT - Jira

XML

Word

Printable

Test case (LIMIT clause is not needed to reproduce the problem, it just makes using ORDER BY reasonable):

--disable_abort_on_error

create table t1 (pk int primary key, c char(1)) engine=LevelDB;

insert into t1 values (1,'a'),(2,'b');

update t1 set c = 'x' order by pk limit 1;

delete from t1 order by pk limit 1;

select * from t1;

Output:

create table t1 (pk int primary key, c char(1)) engine=LevelDB;

insert into t1 values (1,'a'),(2,'b');

update t1 set c = 'x' order by pk limit 1;

ERROR HY000: Lock wait timeout exceeded; try restarting transaction

delete from t1 order by pk limit 1;

ERROR HY000: Lock wait timeout exceeded; try restarting transaction

select * from t1;

pk      c

1       a

2       b

revision-id: psergey@askmonty.org-20130114195003-fgp08gh4swgcf1cx

revno: 4486

branch-nick: mysql-5.6-leveldb

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.