Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-3841 LevelDB storage engine
  3. MDEV-4038

LevelDB: SELECT ... FOR UPDATE does not work for gaps

    XMLWordPrintable

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

      Attachments

        Activity

          People

            psergei Sergei Petrunia
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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