Re: Unexpected Standby Shutdown on sync_replication_slots change

From: shveta malik <shveta(dot)malik(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Xuneng Zhou <xunengzhou(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Hugo DUBOIS <hdubois(at)scaleway(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Subject: Re: Unexpected Standby Shutdown on sync_replication_slots change
Date: 2025-08-05 05:08:33
Message-ID: CAJpy0uCAp1JQ+G+wcicWEh7gFJj7CgF6Unpvq33HxfmFKpt0xA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Aug 4, 2025 at 5:29 PM Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
> On Sat, Aug 2, 2025 at 1:28 PM Xuneng Zhou <xunengzhou(at)gmail(dot)com> wrote:
> > This fix does feel more like an enhancement to user feedback and
> > safety nets, not a correction of a broken or unsafe code path. Unable
> > to start up with the same settings for it might cause
> > more-than-necessary surprise.
>
> Agreed.
>
> At first, since there seems to be rough consensus on applying the current patch
> (which prevents unexpected shutdown while the server is running),
> I've pushed it to master and back-patched it to v17.
>
> As for the follow-up change that prevents the server from starting with
> an invalid configuration, let's continue the discussion. I've attached
> the patch and agree it's a good fit for master.

+1. The patch looks good.

> However, I'm afraid
> it's too late to include it in v18, as beta2 has already been released
> and this change is more of an improvement than a bug fix.
>

If it's not possible to get it to v18 now, then I am okay to have it
on master alone.

thanks
Shveta

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Sajith Prabhakar Shetty 2025-08-05 05:31:36 Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Previous Message Tom Lane 2025-08-05 04:43:06 Re: BUG #19006: Assert(BufferIsPinned) in BufferGetBlockNumber() is triggered for forwarded buffer