Re: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 - Mailing list pgsql-bugs

From David Rowley
Subject Re: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
Date
Msg-id CAApHDvpr=oW77BjkJiLEv1ew_dvUz89wLOvj4RVz4yXFRDSYUQ@mail.gmail.com
Whole thread Raw
In response to BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10  (Ishan Arunkumar Joshi <ishan.joshi@netcracker.com>)
Responses Re: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
RE: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
List pgsql-bugs
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
inPG v16.9. We gone through the Release note for PG v16.10 but not able to find the solution for above mentioned bug
releasedor 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



pgsql-bugs by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
Next
From: Daniel Gustafsson
Date:
Subject: Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore