Request a Demo
Home   >   mailing lists

Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion?
Date
Msg-id CAA4eK1+CrQNqiPDKv1wYfdkbX0FARJoi1=0ioaAqkLzbq2vG1w@mail.gmail.com
Whole thread
In response to Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion?  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion?
List pgsql-hackers
Tree view 
On Wed, Mar 18, 2026 at 9:35 PM Fujii Masao <masao.fujii@gmail.com> 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. Also, we want the last slotsync cycle to complete before
promotion so that chances of subscribers that do failover/switchover
to new primary has better chances of finding failover slots
sync-ready.

--
With Regards,
Amit Kapila.

pgsql-hackers by date:

Previous
From: "Peter 'PMc' Much"
Date:
Subject: Re: Need help debugging SIGBUS crashes
Next
From: "Greg Burd"
Date:
Subject: Add RISC-V Zbb popcount optimization