LevelDB storage engine (MDEV-3841)

[MDEV-4038] LevelDB: SELECT ... FOR UPDATE does not work for gaps Created: 2013-01-14  Updated: 2013-05-27  Resolved: 2013-05-27

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Technical task Priority: Minor
Reporter: Elena Stepanova Assignee: Sergei Petrunia
Resolution: Won't Fix Votes: 0
Labels: leveldb

Issue Links:
Relates

 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



 Comments   
Comment by Elena Stepanova [ 2013-02-06 ]

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.

Generated at Thu Feb 08 06:53:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.