Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, Amit Kapila <amit.kapila16@gmail.com>, vignesh C <vignesh21@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>, Duncan Sands <duncan.sands@deepbluecap.com>, Alexander Lakhin <exclusion@gmail.com>
Date: 2025-06-24T04:58:43Z
Lists: pgsql-bugs
On Tue, Jun 24, 2025 at 10:24:03AM +0900, Masahiko Sawada wrote:
> I've added the patch for that idea for discussion. I considered moving
> the new cache-behavior-dependent test to another test file to minimize
> the maintenance effort but didn't do that at this stage as the test
> file has only a few tests.

The spec test file only includes two short permutations, making the
generated output really short.  A secondary output file sounds fine to
me as long as you document in the spec file the reason why the file is
around, and your patch does that.

+# This file contains cache-behavior-dependent test case. Their reults are
[..]
+# two expected-output files to cvoer both cases. 

Two typos in three lines of comments: s/reults/results/ and
s/cvoer/cover/.
--
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix cache-dependent test failures in logical decoding.

  2. Fix re-distributing previously distributed invalidation messages during logical decoding.

  3. Fix data loss in logical replication.