Avoid getting two snapshots when setting a read_timestamp

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.6, 4.0.0-rc0, WT3.1.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Non-NYC 2018-05-07, Storage Non-NYC 2018-05-21
    • 5

      In WT-3981 we get a new transaction snapshot when setting a read_timestamp in a running transaction.

      That means this pattern:

      session->begin_transaction("isolation=snapshot")
      session->timestamp_transaction("read_timestamp=X")
      

      calls __wt_txn_get_snapshot twice.

      Find a way to avoid one of the calls (while making sure that the snapshot is current as of the timestamp_transaction call for correctness). Setting a read timestamp is a relatively common case, and getting the snapshot can be expensive when many sessions are active.

            Assignee:
            Vamsi Boyapati
            Reporter:
            Michael Cahill (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: