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

Allow read_timestamp to be set after begin_transaction

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.4, 3.7.3, WT3.1.0
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Storage 2018-02-26

      Description

      The WT_SESSION::begin_transaction call can be heavyweight, particularly if the cache is full. Applications may need locking in order to allocate timestamps, so it would be preferable to decouple starting a transaction from timestamp allocation.

      WT already has WT_SESSION::timestamp_transaction for setting commit_timestamp, extend it to also support setting read_timestamp.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                michael.cahill Michael Cahill
                Reporter:
                michael.cahill Michael Cahill
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: