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

Store transaction IDs durably.

    • Type: Icon: New Feature New Feature
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT3.2.0, 4.1.11
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Storage Engines
    • 13
    • Storage Engines 2019-04-08, Storage Engines 2019-04-22, Storage Engines 2019-05-06

      The resolution of the project to read at a timestamp without a snapshot has resulted in agreement that we'll need to include transaction IDs as well as timestamps in the new format changes. There are a two different proposals as how best to do that: either to store transaction IDs in the data file, or to store them in the history file with hints in the data file as to what information is included in the history file. In the latter proposal, hints would be stored either in the data file's leaf pages, or in the address cookie in the internal page that references the leaf page.

            keith.bostic@mongodb.com Keith Bostic (Inactive)
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            0 Vote for this issue
            4 Start watching this issue