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

Fix start_durable_ts when handling out-of-order updates

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.2, 4.4.0-rc0, 4.7.0
    • Component/s: None
    • Labels:
      None

      Description

      Previous fixes for operations with out-of-order timestamps involved changing the effective start timestamp for an operation to match when it has an earlier stop timestamp. The same needs to be done for the (new) start_durable_ts field: when operations are done with out-of-order timestamps, it should be made to match stop_durable_ts.

      Otherwise, an assertion can during reconciliation because start_ts == WT_TS_NONE but start_durable_ts != WT_TS_NONE.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              michael.cahill Michael Cahill
              Reporter:
              michael.cahill Michael Cahill
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: