Request a Demo
Home   >   mailing lists

Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 - Mailing list pgsql-bugs

From Masahiko Sawada
Subject Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Date
Msg-id CAD21AoC7=dVTbE0w_9_7P15e=zmCuw=_Of9JR0=S-hyW+57bEQ@mail.gmail.com
Whole thread Raw
In response to Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 
On Tue, Jun 24, 2025 at 1:18 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Masahiko Sawada <sawada.mshk@gmail.com> writes:
> > Pushed the fix (d87d07b7ad3). Thank you for working on this fix.
>
> There is something not right about the v13 version of this patch.
> BF member trilobite, which builds with -DCLOBBER_CACHE_ALWAYS,
> is showing this failure [1]:

Yes. We've discussed how to fix this test failure and I proposed the
patch for that[1]. If there is no comment and objection, I'm going to
push it to v13.

Regards,

[1] https://www.postgresql.org/message-id/CAD21AoACfSCfWv%3DJtq2AjDyAKspkhNHN7ePvXyASMphYuDJPuw%40mail.gmail.com

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Next
From: Tom Lane
Date:
Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5