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

Switch to a better timestamp and transaction ID ordering convention

    XMLWordPrintable

    Details

    • Type: Technical Debt
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.0, 4.1.11
    • Component/s: None
    • Labels:
      None
    • Story Points:
      8
    • Sprint:
      Storage Engines 2019-05-06

      Description

      The current value (leaf page) timestamp and transaction ID ordering (in structures, function calls and in on-disk cells), is

      start_ts, stop_ts, start_txn, stop_txn

      and the address (internal page) timestamp and transaction ID naming ordering is

      oldest_start_ts, newest_durable_ts, newest_stop_ts, oldest_start_txn, newest_stop_txn 

      This order wasn't chosen for any particular reason, it was a result of an incremental implementation.

      Alexander Gorrod and I would like to switch to

      start_ts, start_txn, stop_ts, stop_txn

      for values, and to

      newest_durable_ts, oldest_start_ts, oldest_start_txn, newest_stop_ts, newest_stop_txn

      for addresses.

      This is 4.1 required because it can't change once it's in the field.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              keith.bostic Keith Bostic
              Reporter:
              keith.bostic Keith Bostic
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: