Re: BUG #17928: Standby fails to decode WAL on termination of primary
От | Thomas Munro |
---|---|
Тема | Re: BUG #17928: Standby fails to decode WAL on termination of primary |
Дата | |
Msg-id | CA+hUKGK1+3rj3c7L9HPCc8HajTVmkTx1CEkU5=rqgV3b4OvWeQ@mail.gmail.com обсуждение исходный текст |
Ответ на | 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 |
On Fri, Sep 22, 2023 at 4:02 PM Michael Paquier <michael@paquier.xyz> wrote: > On Fri, Sep 22, 2023 at 03:11:54PM +1200, Thomas Munro wrote: > > A thought: commit 8fcb32db prevented us from logging messages that are > > too big to be decoded, but it wasn't back-patched. > > Yes, there was one part done in ffd1b6bb6f8 that has required ABI > breakages, as well. There is an argument against a backpatch as a > set of records in a given range may fail to replay while they were > allowed before (I forgot the exact math, but I recall that this was > for records larger than XLogRecordMaxSize, still lower than the max > allocation mark.). Hmm, OK, tricky choices. Anyway, I guess the next thing to straighten out in this area is the OOM policy. Pushed. Thanks Alexander and everyone for the report, testing and help! Time to watch the build farm to see if that Perl turns out to be robust enough...
В списке pgsql-bugs по дате отправления: