Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vBgAY-002qkr-GO for pgsql-bugs@arkaria.postgresql.org; Wed, 22 Oct 2025 21:14:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vBgAX-001LGq-Du for pgsql-bugs@arkaria.postgresql.org; Wed, 22 Oct 2025 21:14:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vBXlS-00FxS7-01 for pgsql-bugs@lists.postgresql.org; Wed, 22 Oct 2025 12:16:25 +0000 Received: from efreedom.netcracker.com ([198.49.86.140]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vBXlO-003bzi-2P for pgsql-bugs@lists.postgresql.org; Wed, 22 Oct 2025 12:16:24 +0000 DKIM-Signature: v=1; a=rsa-sha256; d=netcracker.com; s=i; c=simple/simple; t=1761135381; h=from:subject:to:date:message-id; bh=YV7FG1O4FM20v32sLj17oy3IoVDjSviBm6MZqPfCwtw=; b=JSjQM9OF/cOfG2/ElCpkcEuRfkde9QYEo8UHCB9/HUYpDZK66BSLwXqguYZxWA/g4YXzASwSOL5 2pVXWbRGF/GXtlIw8KfqDT1YrxfJ7Tz33xoOEVzj1vtBne1ZV0iwIHbAkhraL1lpwknDIT/buBWgQ 3QckKKojxluc3CMGBsrWd0SdUiIB4la4wCMaK0whJQMxjp+BIKBFs/1u74JbvtjqWNi9p48QjdEpG K8oaO9qGNiV+M/nF5GIVeiwEFWCP1QxD7BlX4f0wlGAL+dP6XiYa/HPPdbC/NxIuR4JjVM5rwIKFJ Cp+SnwfBgoy6Z8SS8GOJLqglYxyh3vgY7tGA== From: Ishan Arunkumar Joshi To: "pgsql-bugs@lists.postgresql.org" Subject: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 Thread-Topic: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 Thread-Index: AdxDTRSjPswNemdCQrCF5/IthMcDMg== Date: Wed, 22 Oct 2025 12:16:20 +0000 Message-ID: <394a4259f9c64aa89900f4c2a37d8737@netcracker.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_394a4259f9c64aa89900f4c2a37d8737netcrackercom_" MIME-Version: 1.0 X-TM-AS-Product-Ver: SMEX-14.0.0.3223-9.1.2019-29528.007 X-TM-AS-Result: No-10--32.889500-4.000000 X-TMASE-MatchedRID: kwmCtWH83FPz7apsC10gyCQptwyVJHc8Hlyc1f7rlnRIgZxsPm5gYEfd +cHEp3N39nuSKJfmN2gKWMYgJUF+YxW01c+t8bYg1NIaO5sWivjOe9pZzJLe1U7AWg6OqViDOfy LiHKkS3PeTSZ8/m3xawu1/3yQ5QaVfXiG3CQPDN5OdzD1yHlzdDQtZxwUhh6um27y/fpL+iD8WQ niXwYSeuTSw0TOTk7wPcufqILd65vy7moX0TBDBF154oVx0Y26sJRTReM07cw2GdmZM3HbIB/aN EtJTXHvtpPV5/kphnfWpHboRKJMAWAtAznCwv0vmGQxD8bkpeT6fuVSs4vioUVbYbrcAOdR4exJ hDMqBm47T7WJt8RmsGqb+SvQn1G8iQtMmf2it3jGMtCneXAod1pMWq1GqY9jhTLIwRlqj3+6FIM 01sjm5k3WBWNMTSCD2YzUQusciSL2dqN1baggvO4c8DMErak7+FHxOjUevRgTGN/MvLTuwLBOUa WPxmemHz+nRFSeF3IIxpiZuWDGT74zyUR5DYVMdyJ1zNmBVmPWfN4Q+Eg7Qm/zH+B6QMeDMRDB9 vjQu1bYeXOEzfM22YHJkWgsA/RJJU0nG3tpe+CbCOivU2HrC2S0KaInt3A+pfImuORO7j9K+5Mf WBcQH0ISaFVt7T2XQk0WLd0UuxLyJhs1fG15GB/BXqwE9HSW X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-TMASE-Result: 10--32.889500-4.000000 X-TMASE-Version: SMEX-14.0.0.3223-9.1.2019-29528.007 X-TM-SNTS-SMTP: 5DD10E9653EF526ABDFDDEF05CF314064B282A06D5BA928B38F9539C43AA73232000:9 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_394a4259f9c64aa89900f4c2a37d8737netcrackercom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Team, we were facing issue while performing logical replication error as follows = which are similar to BUG 18942 and 18938 in PG v16.9. We gone through the R= elease note for PG v16.10 but not able to find the solution for above menti= oned bug released or not. can you please help to understand if the solution is available for BUG 1894= 2 and 18938 in latest PG16 release 16.10. Error in PG v16.9 PostgreSQL Streaming Replication error while retrieving PostgreSQL logical = log records: -1 : ERROR: invalid memory alloc request size 1803546384. The previous error occurred after scanning record 31, which has timeline+LS= N+previousLSN 0+DD0A/2CBE4708+0/0 and timestamp 2025-07-09T12:13:04+07:00. Thanks & Regards, ------------------------- Ishan Joshi ________________________________ The information transmitted herein is intended only for the person or entit= y to which it is addressed and may contain confidential, proprietary and/or= privileged material. Any review, retransmission, dissemination or other us= e of, or taking of any action in reliance upon, this information by persons= or entities other than the intended recipient is prohibited. If you receiv= ed this in error, please contact the sender and delete the material from an= y computer. --_000_394a4259f9c64aa89900f4c2a37d8737netcrackercom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Team,

we were facing issue while performing logical replication error as follows = which are similar to BUG 18942 and 18938 in PG v16.9. We gone through the R= elease note for PG v16.10 but not able to find the solution for above menti= oned bug released or not.

can you please help to understand if the solution is available for BUG 1894= 2 and 18938  in latest PG16 release 16.10.


Error in PG v16.9
PostgreSQL = Streaming Replication error while retrieving PostgreSQL logical log records= : -1 : ERROR: invalid memory alloc request size 1803546384.  
The previous error occurred after scanning record 31, which has timeline= 3;LSN+previousLSN 0+DD0A/2CBE4708+0/0 and timestamp 2025-07-09T= 12:13:04+07:00.

 

 

 

Thanks & Regards,

-----------= --------------
Ishan Joshi

 

=  

=

The information transmitted herein is intended only for the person or entit= y to which it is addressed and may contain confidential, proprietary and/or= privileged material. Any review, retransmission, dissemination or other us= e of, or taking of any action in reliance upon, this information by persons or entities other than the inte= nded recipient is prohibited. If you received this in error, please contact= the sender and delete the material from any computer.  

--_000_394a4259f9c64aa89900f4c2a37d8737netcrackercom_--