Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-4158

Fix concurrent behaviour of insert with truncate.

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None

      At the moment if a range truncate is started over a range of keys, and in parallel another transaction inserts a key into that range, the behavior is not well defined - a conflict may be detected or both transactions may be permitted to commit. If they do commit, then there is a crash and recovery runs, the result may be different than what was in cache before the crash.

        1. test_truncate04.py
          3 kB
        2. test_truncate04a.py
          13 kB

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            vamsi.krishna@mongodb.com Vamsi Boyapati
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: