Ensure all WT_CURSOR API calls go through WiredTigerCursor and are thread-safe

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Server Integration
    • SongingMoose - 2025-01-07, NamePending - 2025-01-21, MooseOnTheLoose - 2025-02-04
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This is follow on work from SERVER-98126. Any WT_CURSOR's should be protected the same way its owning WT_SESSION, to prevent concurrent cursor operations with a rollback.

            Assignee:
            Nic Hollingum
            Reporter:
            Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: