Details
-
Technical task
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
One connection reserves an empty spot for a PK using SELECT .. FOR UPDATE, but another connection is still able to insert there. For InnoDB the test case works as expected.
--enable_connect_log
|
|
|
create table t1 (pk int primary key, i int) engine=LevelDB; |
insert into t1 values (1,1),(2,2); |
|
|
begin; |
select * from t1 where pk = 3 for update; |
|
|
--connect (con1,localhost,root,,)
|
--error ER_LOCK_WAIT_TIMEOUT
|
insert into t1 values (3,300); |
|
|
--connection default
|
rollback; |
|
|
mysqltest: At line 11: query 'insert into t1 values (3,300)' succeeded - should have failed with errno 1205...
|
revision-id: psergey@askmonty.org-20130114131529-qv3531bw9fdklwob
|
revno: 4483
|
branch-nick: mysql-5.6-leveldb
|
Reproducible on
revision-id: psergey@askmonty.org-20130201180328-ocmbh9uvcoedmihp
revno: 4591
branch-nick: mysql-5.6-leveldb
but we haven't decided yet whether it's a bug at all.