Rework dbtest's WriteContextForTests to not hold locks for its lifetime

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      WriteContextForTests holds DB and collections locks for its lifetime. This should not be needed, as the way. for query code to acquire catalog resources and locks should be through the ShardRole API. However, many of the dbtests rely on WriteContextForTests holding locks because they later run DDL functions that require the locks to be held.

              Assignee:
              Unassigned
              Reporter:
              Jordi Serra Torrens
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: