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

Allow read_timestamp to be set after begin_transaction

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

      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.

            Assignee:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Reporter:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: