On Mon, Mar 23, 2026 at 11:21 AM Fujii Masao <[email protected]> wrote: > > On Sun, Mar 22, 2026 at 1:52 AM Amit Kapila <[email protected]> wrote: > > > > On Wed, Mar 18, 2026 at 9:35 PM Fujii Masao <[email protected]> wrote: > > > > > > I noticed that during standby promotion the startup process sends SIGUSR1 > > > to > > > the slotsync worker to make it exit. Is there a reason for using SIGUSR1? > > > > > > > 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. -- With Regards, Amit Kapila.
