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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Duncan Sands <duncan(dot)sands(at)deepbluecap(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Date: 2025-06-24 04:34:26
Message-ID: 859850.1750739666@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> writes:
> On Tue, Jun 24, 2025 at 1:18 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> There is something not right about the v13 version of this patch.

> 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.

Oh, my apologies for not having kept up on that thread!

Both of the proposed patches seem like band-aids, but I'm not
sure that it's worth working harder on a branch that has only
a few months to live. I'm okay with either solution.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2025-06-24 04:58:43 Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Previous Message Masahiko Sawada 2025-06-24 04:22:53 Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5