Re: 024_add_drop_pub.pl might fail due to deadlock
От | Amit Kapila |
---|---|
Тема | Re: 024_add_drop_pub.pl might fail due to deadlock |
Дата | |
Msg-id | CAA4eK1J0qFm6QRc4wcbq19P4PcSWnB=i+f6n1m8njweoD87xaQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: 024_add_drop_pub.pl might fail due to deadlock (vignesh C <vignesh21@gmail.com>) |
Список | pgsql-hackers |
On Thu, Jul 31, 2025 at 2:37 PM vignesh C <vignesh21@gmail.com> wrote: > > How about we change the below: > +#ifdef USE_ASSERT_CHECKING > + LOCKTAG tag; > +#endif > + > + Assert(CheckRelationOidLockedByMe(SubscriptionRelRelationId, > + > RowExclusiveLock, true)); > + > + rel = table_open(SubscriptionRelRelationId, NoLock); > +#ifdef USE_ASSERT_CHECKING > + SET_LOCKTAG_OBJECT(tag, InvalidOid, > SubscriptionRelationId, subid, 0); > + Assert(LockHeldByMe(&tag, AccessShareLock, true)); > +#endif > > to: > #ifdef USE_ASSERT_CHECKING > LOCKTAG tag; > Assert(CheckRelationOidLockedByMe(SubscriptionRelRelationId, > RowExclusiveLock, true)); > SET_LOCKTAG_OBJECT(tag, InvalidOid, SubscriptionRelationId, subid, 0); > Assert(LockHeldByMe(&tag, AccessShareLock, true)); > #endif > > rel = table_open(SubscriptionRelRelationId, NoLock); > } > Your suggested change looks better to me. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: