RE: 024_add_drop_pub.pl might fail due to deadlock
От | Hayato Kuroda (Fujitsu) |
---|---|
Тема | RE: 024_add_drop_pub.pl might fail due to deadlock |
Дата | |
Msg-id | OS7PR01MB149682E5CAA567A7798BC6BA9F525A@OS7PR01MB14968.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: 024_add_drop_pub.pl might fail due to deadlock (Ajin Cherian <itsajin@gmail.com>) |
Ответы |
Re: 024_add_drop_pub.pl might fail due to deadlock
|
Список | pgsql-hackers |
Dear Ajin, > Thanks for your review Kuroda-san, I have changed the logic to not use > already_locked and instead check if the locks are taken inside > UpdateSubscriptionRelState itself. I've tested this and this works > fine. If this logic is acceptable to the reviewers I can update the > other patches also in a similar way. Thanks for updates. However, I found that functions like LockHeldByMe(), CheckRelationOidLockedByMe() and LWLockHeldByMe() have been used only for the debug build. Functions like ProcArraySetReplicationSlotXmin() and MarkAsPrepared() can remove the flag from the argument but they are retained till now. Based on that, I suggest adding new argument (or add new Ex function for bank branches) and do the assertion check when the assertion is enabled in this build. Thought? Best regards, Hayato Kuroda FUJITSU LIMITED
В списке pgsql-hackers по дате отправления: