Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Masahiko Sawada <sawada.mshk@gmail.com>
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>,
Amit Kapila <amit.kapila16@gmail.com>, Duncan Sands <duncan.sands@deepbluecap.com>, vignesh C <vignesh21@gmail.com>
Date: 2025-06-02T18:08:54Z
Lists: pgsql-bugs
On Mon, Jun 2, 2025 at 4:35 AM Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com> wrote: > > Dear Amit, Duncan, Vignesh, Sawada-san, > > I searched on GitHub and confirmed that no extensions use sizeof(ReorderBufferTXN). > Based on that, can we proceed with the fix for backbenches? > Note that I checked only repositories that are opened on GitHub. Proprietary > ones and hosting on other services cannot be guaranteed. > > How I search > =========== > I searched on github with "sizeof(ReorderBufferTXN)", and 259 files were found. > All of them were either "reorderbuffer.c" or "reorderbuffer.cpp". reorderbuffer.c > came from the forked postgres repos, and "reorderbuffer.cpp" came from the > openGauss project, which tries to enhance postgres. In both cases, they are > server-side code and will rebase community's commits when we update the header > file and sizeof(ReorderBufferTXN). > In this check, I could not find extensions that refer to the size; only > server-side codes were found. Based on that, we could extend the struct > ReorderBufferTXN. Thank you for checking the source codes on Github. I personally think the chance that extensions depend on the ReorderBufferTXN size is low. Without that, we would need more complex logic to store inval messages per-transaction, which introduce a risk. So I agree with the current solution. Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix cache-dependent test failures in logical decoding.
- 87819f766f37 13.22 landed
-
Fix re-distributing previously distributed invalidation messages during logical decoding.
- d87d07b7ad3b 18.0 landed
- 45c357e0e85d 17.6 landed
- b2ae077205e1 16.10 landed
- fc0fb77c550f 15.14 landed
- 983b3636259b 14.19 landed
- 1230be12f086 13.22 landed
-
Fix data loss in logical replication.
- 247ee94150b6 13.21 cited
- 4909b38af034 18.0 cited