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

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Ajin Cherian <itsajin(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-03 11:19:03
Message-ID: CAA4eK1+Mu3NzkTxE92ugYHA4-rYmP=WQ9733tFvLTc1eZNdUuQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2025-12-03 11:26:49 Re: Proposal: Conflict log history table for Logical Replication
Previous Message Bertrand Drouvot 2025-12-03 11:17:43 Re: Safer hash table initialization macro