Re: 024_add_drop_pub.pl might fail due to deadlock

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Ajin Cherian <itsajin(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 024_add_drop_pub.pl might fail due to deadlock
Date: 2025-07-29 12:55:28
Message-ID: CALDaNm3rnu=bdeZgipfsqnf1kdjZ1b-L+7ynphWAoCAD7Y-_ew@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 29 Jul 2025 at 14:46, Ajin Cherian <itsajin(at)gmail(dot)com> wrote:
>
> On Tue, Jul 29, 2025 at 1:13 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> >
> > Yes, that makes sense to me. For HEAD and PG18, we can still add a new
> > argument to the API. For other bank branches, it is better to use a
> > new Ex function as suggested by Kuroda-San.
> >
>
> Here are the updated patches.

The only case where the ordering of lock now is different is in
DropSubscription, but in this case we take an AccessExclusiveLock on
pg_subscription which should prevent this deadlock from occurring:
...
replorigin_drop_by_name(originname, true, false);
}

/* Clean up dependencies */
deleteSharedDependencyRecordsFor(SubscriptionRelationId, subid, 0);

/* Remove any associated relation synchronization states. */
RemoveSubscriptionRel(subid, InvalidOid);
...

Regards,
Vignesh

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-07-29 12:57:07 Re: C11 / VS 2019
Previous Message Euler Taveira 2025-07-29 12:52:37 Re: event trigger support for PL/Python