MIME-Version: 1.0
References: 
 <CAHGQGwFzNYroAxSoyJhqTU-pH=t4Ej6RyvhVmBZ91Exj_TPMMQ@mail.gmail.com>
 <CAA4eK1+CrQNqiPDKv1wYfdkbX0FARJoi1=0ioaAqkLzbq2vG1w@mail.gmail.com>
 <CAHGQGwHABvuCoyM24HUiFZ5oJq_CoFomjt_cqD-0cJLMjFXJjQ@mail.gmail.com>
In-Reply-To: 
 <CAHGQGwHABvuCoyM24HUiFZ5oJq_CoFomjt_cqD-0cJLMjFXJjQ@mail.gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
Date: Tue, 24 Mar 2026 15:07:19 +0530
Message-ID: 
 <CAA4eK1KQy4Bzr39HvMdrz1_58s8b0UwpBk9KqrbTD3GK=OHt1g@mail.gmail.com>
Subject: Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during
 promotion?
To: Fujii Masao <masao.fujii@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAA4eK1KQy4Bzr39HvMdrz1_58s8b0UwpBk9KqrbTD3GK%3DOHt1g%40mail.gmail.com>
Precedence: bulk

On Mon, Mar 23, 2026 at 11:21=E2=80=AFAM Fujii Masao <masao.fujii@gmail.com=
> wrote:
>
> On Sun, Mar 22, 2026 at 1:52=E2=80=AFAM Amit Kapila <amit.kapila16@gmail.=
com> wrote:
> >
> > On Wed, Mar 18, 2026 at 9:35=E2=80=AFPM Fujii Masao <masao.fujii@gmail.=
com> wrote:
> > >
> > > I noticed that during standby promotion the startup process sends SIG=
USR1 to
> > > the slotsync worker to make it exit. Is there a reason for using SIGU=
SR1?
> > >
> >
> > IIRC, this same signal is used for both the backend executing
> > pg_sync_replication_slots() and slotsync worker. We want the worker to
> > exit and error_out backend. Using SIGTERM for backend could result in
> > its exit.
>
> Why do we want the backend running pg_sync_replication_slots() to throw
> an error here, rather than just exit?
>

I think it was because the backends remain connected after promotion
and if we make them exit that will change the existing behavior.

--=20
With Regards,
Amit Kapila.