Fix concurrent behaviour of insert with truncate.

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • 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:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              Vamsi Boyapati
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: