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

Enhance WT_CURSOR::reserve documentation around commit visibility

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • None
    • 3.6.9, 4.0.1, 4.1.1, WT3.2.0
    • None
    • None
    • 2
    • Storage Non-NYC 2018-07-02

    Description

      Our current documentation for WT_CURSOR::reserve doesn't explain that on commit the transaction no longer references the reserved slot, and so other transactions with this transaction in their snapshot will no longer conflict with the reserve operation.

      i.e: the WT_UPDATE structure that was created as part of the reserve operation has it's transaction ID set to WT_TXN_NONE on transaction commit.

      Attachments

        Activity

          People

            sulabh.mahajan@mongodb.com Sulabh Mahajan
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: