Avoid repeated copy of ViewsForDatabase in UncommittedCatalogUpdates

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As a result of SERVER-57250, view DDL operations will atomically replace the ViewsForDatabase object. If two or more such operations happen in the same storage transaction, each will register a full copy of the ViewsForDatabase object with the UncommittedCatalogUpdates class. We could probably refactor this in such a way that if we already have a copy stored in UncommittedCatalogUpdates, we can modify it directly rather than creating an additional copy.

            Assignee:
            Unassigned
            Reporter:
            Dan Larkin-York
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: