Fix behavior of fast-truncate when conflicting with a prior remove

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor - P4
    • WT11.0.0, 5.3.0, 5.2.0-rc2
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage - Ra 2022-01-10
    • None

      The row-store fast-truncate code fails to detect conflicts with removes that have already been committed to candidate pages, because it checks only the page's aggregated start time and not also the stop time.

              Assignee:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              David Holland
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: