Fix session->ncursors behaviour within clayered cursors

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Layered Tables
    • Security Level: Public (Available to anyone on the web)
    • Storage Engines - Foundations
    • 4,862.586
    • None
    • 3

      Inside clayered_enter and clayered_leave we increase and decrease session->ncursors. We need to re-evaluate whether this is okay and need at all.

      We also have a strange if condition for the __wt_txn_read_committed_should_release_snapshot function that cause cursors to be reset. 

      That's probably because of this code from the file cursor:

       

      /*
       * When the count of active cursors in the session goes to zero, there are no active cursors, and we can release any snapshot we're
       * holding for read committed isolation.
       */
       if (session->ncursors == 0 && !WT_READING_CHECKPOINT(session))
           __wt_txn_read_last(session);

      We should check whether we can simply remove the condition for __wt_txn_read_committed_should_release_snapshot together with the function.
       

            Assignee:
            Jie Chen
            Reporter:
            Jie Chen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: