Re: Improve pg_sync_replication_slots() to wait for primary to advance

From: Ajin Cherian <itsajin(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: shveta malik <shveta(dot)malik(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve pg_sync_replication_slots() to wait for primary to advance
Date: 2025-12-04 05:21:39
Message-ID: CAFPTHDY+sXkLVOgsjQJoLEsmuNJXpAhQ0uqb1DQ_bVE3Zq3oHQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 3, 2025 at 10:19 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Wed, Dec 3, 2025 at 8:51 AM Ajin Cherian <itsajin(at)gmail(dot)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 Content-Type Size
v29-0001-Use-SIGUSR1-to-interrupt-slot-synchronization-wo.patch application/octet-stream 10.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2025-12-04 05:30:52 Re: tuple radix sort
Previous Message Tom Lane 2025-12-04 05:19:08 Something in our JIT code is screwing up PG_PRINTF_ATTRIBUTE