Re: Unexpected Standby Shutdown on sync_replication_slots change
От | Laurenz Albe |
---|---|
Тема | Re: Unexpected Standby Shutdown on sync_replication_slots change |
Дата | |
Msg-id | dcd0941f0ddb0b0c9b5299cc1277fc0153532ef4.camel@cybertec.at обсуждение исходный текст |
Ответ на | Re: Unexpected Standby Shutdown on sync_replication_slots change (Fujii Masao <masao.fujii@gmail.com>) |
Ответы |
Re: Unexpected Standby Shutdown on sync_replication_slots change
|
Список | 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
В списке pgsql-bugs по дате отправления: