Re: BUG #17928: Standby fails to decode WAL on termination of primary
От | Tom Lane |
---|---|
Тема | Re: BUG #17928: Standby fails to decode WAL on termination of primary |
Дата | |
Msg-id | 351991.1691800320@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #17928: Standby fails to decode WAL on termination of primary (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: BUG #17928: Standby fails to decode WAL on termination of primary
|
Список | pgsql-bugs |
Michael Paquier <michael@paquier.xyz> writes: > On Sat, Aug 12, 2023 at 11:56:45AM +1200, Thomas Munro wrote: >> On Sat, Aug 12, 2023 at 2:00 AM Noah Misch <noah@leadboat.com> wrote: >>> I recall earlier messages theorizing that it was just harder to hit in v14, so >>> I'm disinclined to stop at v15. I think the main choice is whether to stop at >>> v11 (normal choice) or v12 (worry about breaking the last v11 point release). >>> I don't have a strong opinion between those. > Okay. I wouldn't be inclined to patch v11 for that, FWIW, as this > code path is touched by recovery and more. At least it does not seem > worth taking any risk compared to the potential gain. That was my gut reaction too -- risk/reward seems not great for the last v11 release. (I've been burned a couple of times now by putting can't-fix-it-anymore bugs into the final release of a branch, so maybe I'm just being overly paranoid. But it's something to worry about.) regards, tom lane
В списке pgsql-bugs по дате отправления: