From: Ishan Arunkumar Joshi <ishan.joshi@netcracker.com>
To: David Rowley <dgrowleyml@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: RE: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
Date: Thu, 23 Oct 2025 04:48:20 +0000
Message-ID: <4cd89092e95d48d297039824b0c804c6@netcracker.com> (raw)
In-Reply-To: <CAApHDvpr=oW77BjkJiLEv1ew_dvUz89wLOvj4RVz4yXFRDSYUQ@mail.gmail.com>
References: <394a4259f9c64aa89900f4c2a37d8737@netcracker.com>
<CAApHDvpr=oW77BjkJiLEv1ew_dvUz89wLOvj4RVz4yXFRDSYUQ@mail.gmail.com>
Hello David,
Thanks for your reply but I think that is separate issue that is mentioned in the release note. As the bug are related to memory allocation while logical replication slots is been configured ("invalid memory alloc request size 1803546384") where the release note is related to partialy written WAL which is not the use case.
Thanks & Regards,
-------------------------
Ishan Joshi
-----Original Message-----
From: David Rowley <dgrowleyml@gmail.com>
Sent: Thursday, October 23, 2025 3:07 AM
To: Ishan Arunkumar Joshi <ishan.joshi@netcracker.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
[External Email]
________________________________
On Thu, 23 Oct 2025 at 10:14, Ishan Arunkumar Joshi <ishan.joshi@netcracker.com> wrote:
> 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 Release note for PG v16.10 but not able to find the solution for above mentioned bug released or not.
>
> can you please help to understand if the solution is available for BUG 18942 and 18938 in latest PG16 release 16.10.
Yes. Mentioned in: https://www.postgresql.org/docs/16/release-16-10.html
"Avoid infinite wait in logical decoding when reading a partially-written WAL record (Vignesh C) ยง
If the server crashes after writing the first part of a WAL record that would span multiple pages, subsequent logical decoding of the WAL stream would wait for data to arrive on the next WAL page. That might never happen if the server is now idle."
David
________________________________
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
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: ishan.joshi@netcracker.com, dgrowleyml@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: RE: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
In-Reply-To: <4cd89092e95d48d297039824b0c804c6@netcracker.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