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

Remove the stop timestamp from the WT_UPDATE structure

    • Type: Icon: Technical Debt Technical Debt
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • WT3.2.0, 4.1.11
    • Affects Version/s: None
    • Component/s: None
    • None
    • 3
    • Storage Engines 2019-04-22, Storage Engines 2019-05-06

      Remove the WT_UPDATE.stop_ts field.

      michael.cahill comments:
      Stop timestamps should only be calculated when traversing an update list (if we see a tombstone that isn't stable, its commit timestamp becomes the stop timestamp for the subsequent value). There should never be a stop timestamp for an update: we'd create a tombstone if we needed to represent that.

            Assignee:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Reporter:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: