> locked. I've made a new version of the patch on PG_15. I've made a similar fix on HEAD just so that the code is now consistent. I don't think the similar problem (deadlock between two different subscriptions trying to drop tracking origin) occurs on HEAD with my previous patch, as the way origins are dropped are different on HEAD. On HEAD, while dropping origin, a RowExclusiveLock lock is taken on ReplicationOriginRelationId and then an AccessExclusiveLock is taken on the particular origin. Since the particular origin will be different on different subscriptions, the similar deadlock will not happen. But just to keep code consistent, I have made a similar fix.
regards, Ajin Cherian Fujitsu Australia
HEAD-v3-0001-Fix-a-possible-deadlock-during-ALTER-SUBSCRIPTION.patch
Description: Binary data
