From: Duncan Sands <duncan.sands@deepbluecap.com>
To: Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Cc: Sawada Masahiko <sawada.mshk@gmail.com>
Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Date: Wed, 21 May 2025 15:27:31 +0200
Message-ID: <75edd9d3-d861-4dd0-b190-180cc034ceba@deepbluecap.com> (raw)
In-Reply-To: <OSCPR01MB14966139B6C89C27647712A90F59EA@OSCPR01MB14966.jpnprd01.prod.outlook.com>
References: <680bdaf6-f7d1-4536-b580-05c2760c67c6@deepbluecap.com>
<CAA4eK1JwJw6JOnfDxtGtSRF7kM0LbEVPRmNxWeJa5+wyoG05Xg@mail.gmail.com>
<CAA4eK1LMgqeT_bPZ3MH-VKvwOqpZyfJmF7knZhu1rqt2Pqsnwg@mail.gmail.com>
<OSCPR01MB14966139B6C89C27647712A90F59EA@OSCPR01MB14966.jpnprd01.prod.outlook.com>
> Based on the analysis, I created a PoC which avoids the repalloc().
> Invalidation messages distributed by SnapBuildDistributeSnapshotAndInval() are
> skipped to add in the list, just queued - repalloc can be skipped. Also, the function
> distributes messages only in the list, so received messages won't be sent again.
>
> Now a patch for PG17 is created for testing purpose. Duncan, can you apply this and
> confirms whether the issue can be solved?
Thanks Hayato Kuroda, will do, however it may take a few days.
Best wishes, Duncan.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: duncan.sands@deepbluecap.com, kuroda.hayato@fujitsu.com, amit.kapila16@gmail.com, pgsql-bugs@lists.postgresql.org, sawada.mshk@gmail.com
Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
In-Reply-To: <75edd9d3-d861-4dd0-b190-180cc034ceba@deepbluecap.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox