Re: Replication slot drop message is sent after pgstats shutdown. - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Replication slot drop message is sent after pgstats shutdown.
Date
Msg-id 20210831173936.czhs75gjcl2kacfh@alap3.anarazel.de
Whole thread Raw
In response to Re: Replication slot drop message is sent after pgstats shutdown.  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: Replication slot drop message is sent after pgstats shutdown.  (Masahiko Sawada <sawada.mshk@gmail.com>)
List 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 by date:

Previous
From: John Naylor
Date:
Subject: Re: Patch: shouldn't timezone(text, timestamp[tz]) be STABLE?
Next
From: Tom Lane
Date:
Subject: Re: Patch: shouldn't timezone(text, timestamp[tz]) be STABLE?