mirror of
https://github.com/postgres/postgres.git
synced 2025-07-07 00:36:50 +03:00
Heed lock protocol in DROP OWNED BY
We were acquiring object locks then deleting objects one by one, instead of acquiring all object locks first, ignoring those that did not exist, and then deleting all objects together. The latter is the correct protocol to use, and what this commits changes to code to do. Failing to follow that leads to "cache lookup failed for relation XYZ" error reports when DROP OWNED runs concurrently with other DDL -- for example, a session termination that removes some temp tables. Author: Álvaro Herrera Reported-by: Mithun Chicklore Yogendra (Mithun CY) Reviewed-by: Ahsan Hadi, Tom Lane Discussion: https://postgr.es/m/CADq3xVZTbzK4ZLKq+dn_vB4QafXXbmMgDP3trY-GuLnib2Ai1w@mail.gmail.com
This commit is contained in:
@ -915,7 +915,6 @@ DropSubscription(DropSubscriptionStmt *stmt, bool isTopLevel)
|
||||
if (slotname)
|
||||
PreventInTransactionBlock(isTopLevel, "DROP SUBSCRIPTION");
|
||||
|
||||
|
||||
ObjectAddressSet(myself, SubscriptionRelationId, subid);
|
||||
EventTriggerSQLDropAddObject(&myself, true, true);
|
||||
|
||||
|
Reference in New Issue
Block a user