Re: Replication slot drop message is sent after pgstats shutdown.
От | Andres Freund |
---|---|
Тема | Re: Replication slot drop message is sent after pgstats shutdown. |
Дата | |
Msg-id | 20210831173936.czhs75gjcl2kacfh@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Replication slot drop message is sent after pgstats shutdown. (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Ответы |
Re: Replication slot drop message is sent after pgstats shutdown.
|
Список | pgsql-hackers |
Hi, On 2021-08-31 18:34:12 +0900, Kyotaro Horiguchi wrote: > At Tue, 31 Aug 2021 17:14:45 +0900, Masahiko Sawada <sawada.mshk@gmail.com> wrote in > > On Tue, Aug 31, 2021 at 2:34 PM Andres Freund <andres@anarazel.de> wrote: > > > > > > On 2021-08-31 14:22:39 +0900, Masahiko Sawada wrote: > > > > You mean to move only the part of sending the message to its own > > > > before_shmem_exit() callback? or move ReplicationSlotRelease() and > > > > ReplicationSlotCleanup() from ProcKill() to it? > > > > > > The latter. > > > > Makes sense. > > > > I've attached the patch that moves them to its own > > before_shmem_exit(). Unless I missed to register the callback it works > > the same as before except for where to release and clean up the slots. > > Is there any reason we need to register the callback dynamically? It > seems to me what we need to do here is to call the functions at > before-shmem-exit. +1. I'd just add a ReplicationSlotInitialize() to BaseInit(). Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: