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

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Masahiko Sawada' <sawada(dot)mshk(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Duncan Sands <duncan(dot)sands(at)deepbluecap(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>
Subject: RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Date: 2025-06-23 12:03:33
Message-ID: OSCPR01MB14966CD70FA2144C1F972647BF579A@OSCPR01MB14966.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Dear Sawada-san,

> One solution is to have two expected-output files to cover both cases.
> We do a similar thing for the plpgsql_cache.sql test case. What do you
> think?

Personally I don't like the approach because XXX_1.out can be easily missed to be
updated, but it is not a strong opinion.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Masahiko Sawada 2025-06-23 14:05:35 Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Previous Message Richard Guo 2025-06-23 09:13:49 Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references