Re-evaluate the value that session->name brings

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Not Applicable
    • None
    • Storage Engines - Foundations
    • None
    • 3

      Currently, we have a session::name field that is redefined every time we enter or leave any user-visible API. However, the value of this logic is not obvious, and, as discovered in WT-16496, when it is used by multiple threads simultaneously it can even cause confusion by reporting the wrong name.

      The scope of this ticket is to evaluate whether session->name provides any meaningful value and to remove it if it does not.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Ivan Kochin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: