The profile command should not take a MODE_X db lock at level 0

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      At level 0 we are either setting the slowms or sampleRate global values which does not require a database lock or if the database exists, setting the profiling level to 0 which requires at most a MODE_S lock.

      It is worth noting that Locker and RecoveryUnit stashing for transactions will block MODE_X acquisition on a participating database. This will make this issue more visible for those using transactions.

            Assignee:
            Backlog - Query Team (Inactive)
            Reporter:
            James Wahlin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: