Re: Improve pg_sync_replication_slots() to wait for primary to advance - Mailing list pgsql-hackers

From Ajin Cherian
Subject Re: Improve pg_sync_replication_slots() to wait for primary to advance
Date
Msg-id CAFPTHDY+sXkLVOgsjQJoLEsmuNJXpAhQ0uqb1DQ_bVE3Zq3oHQ@mail.gmail.com
Whole thread Raw
In response to Re: Improve pg_sync_replication_slots() to wait for primary to advance  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Improve pg_sync_replication_slots() to wait for primary to advance
List pgsql-hackers
On Wed, Dec 3, 2025 at 10:19 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Wed, Dec 3, 2025 at 8:51 AM Ajin Cherian <itsajin@gmail.com> wrote:
> >
> > Attaching patch v28 addressing these comments.
> >
>
> Can we extract the part of the patch that handles SIGUSR1 signal
> separately as a first patch and the remaining as a second patch?
> Please do mention the reason in the commit message as to why we are
> changing the signal for SIGINT to SIGUSR1.
>

I have extracted out the SIGUSR1 signal handling changes separately
into a patch and sharing. I will share the next patch later.
Let me know if there are any comments for this patch.

regards,
Ajin Cherian
Fujitsu Australia

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Something in our JIT code is screwing up PG_PRINTF_ATTRIBUTE
Next
From: John Naylor
Date:
Subject: Re: tuple radix sort