Re: Unexpected Standby Shutdown on sync_replication_slots change

From: shveta malik <shveta(dot)malik(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, 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-07-30 03:15:20
Message-ID: CAJpy0uCETspZ_ZN-vMNJYFhhQtkG-UrLuK7M5fZu1_AnGMC8rw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jul 29, 2025 at 12:04 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> On Tue, 2025-07-29 at 13:40 +0900, Fujii Masao wrote:
> > I think it's basically not acceptable for a server to start up
> > successfully before a minor version update, but then fail to start with
> > the same configuration after the update. If that's absolutely necessary
> > to fix a bug, it might be justifiable. But in this case, I don't think
> > it's required.
> >
> > Blocking startup when sync_replication_slots is enabled and wal_level
> > is not logical could be helpful. But that feels more like an improvement
> > than a bug fix. I'm fine adding that to master, but I don't think we should
> > apply it to old branches.
> >
> > That said, both Shveta and Amit support backpatching this change,
> > so I'd like to hear more opinions before we decide.
>
> I side with you on that one.
>
> I think it would be fine to backpatch the breaking change to v18,
> if we mention the behavior change in the release notes.
>

I am fine with the suggestion.

thanks
Shveta

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-07-30 03:27:35 Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
Previous Message Samuel Marks 2025-07-30 03:01:16 Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`