From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | shveta malik <shveta(dot)malik(at)gmail(dot)com>, Hugo DUBOIS <hdubois(at)scaleway(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Unexpected Standby Shutdown on sync_replication_slots change |
Date: | 2025-07-29 06:34:52 |
Message-ID: | dcd0941f0ddb0b0c9b5299cc1277fc0153532ef4.camel@cybertec.at |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2025-07-29 13:55:07 | BUG #19001: PostgreSQL 17: CREATE MATERIALIZED VIEW fails with STABLE function using JSONB LATERAL joins |
Previous Message | Sajith Prabhakar Shetty | 2025-07-29 05:49:15 | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |