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

From: Ajin Cherian <itsajin(at)gmail(dot)com>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(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 09:01:04
Message-ID: CAFPTHDar6dkEmq=ZD5tgrsDkG2kPZMKWuXBd8XR+nomtzbugMQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 4, 2025 at 5:04 PM shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
>
>
> I have just 2 trivial comments for v29-001:
>
> 1)
> -   * receives a SIGINT from the startup process, or when there is an error.
> +   * receives a SIGUSR1 from the startup process, or when there is an error.
>
> In above we should mention stopSignaled rather than SIGUSR1, as
> SIGUSR1 is just a wakeup signal and not termination signal.
>

Fixed.

> 2)
> +    else
> +      ereport(ERROR,
> +          errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE),
> +          errmsg("cannot continue replication slot synchronization"
> +             " as standby promotion is triggered"));
>
> Please mention that it is SQL-function in the comment for else-block.
>

Fixed.

> ~~
>
> I tested the touched scenarios and here are the LOGs:
>

Thanks for testing!

Attaching patch v30 with the above changes addressed. I've also run
pgindent on the changes.

regards,
Ajin Cherian
Fujitsu Australia

Attachment Content-Type Size
v30-0001-Use-SIGUSR1-to-interrupt-slot-synchronization-wo.patch application/octet-stream 10.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-12-04 09:10:42 Re: Cleanup shadows variable warnings, round 1
Previous Message Michael Paquier 2025-12-04 08:48:59 Re: Fix crash during recovery when redo segment is missing