From: Euler Taveira <euler@eulerto.com>
To: David Rowley <dgrowleyml@gmail.com>
To: Ishan Arunkumar Joshi <ishan.joshi@netcracker.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: Wed, 22 Oct 2025 19:41:37 -0300
Message-ID: <0108521d-96ec-4ed9-9fb3-2183547ac13c@app.fastmail.com> (raw)
In-Reply-To: <CAApHDvpr=oW77BjkJiLEv1ew_dvUz89wLOvj4RVz4yXFRDSYUQ@mail.gmail.com>
References: <394a4259f9c64aa89900f4c2a37d8737@netcracker.com>
<CAApHDvpr=oW77BjkJiLEv1ew_dvUz89wLOvj4RVz4yXFRDSYUQ@mail.gmail.com>
On Wed, Oct 22, 2025, at 6:36 PM, David Rowley wrote:
> 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) ยง
>
This is not the current fix. The one for the referred bugs is:
Avoid re-distributing cache invalidation messages from other transactions
during logical replication (vignesh C)
Our previous round of minor releases included a bug fix to ensure that
replication receiver processes would respond to cross-process cache
invalidation messages, preventing them from using stale catalog data while
performing replication updates. However, the fix unintentionally made them also
redistribute those messages again, leading to an exponential increase in the
number of invalidation messages, which would often end in a memory allocation
failure. Fix by not redistributing received messages.
The commit for v16 is b2ae077205e.
--
Euler Taveira
EDB https://www.enterprisedb.com/
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: euler@eulerto.com, dgrowleyml@gmail.com, ishan.joshi@netcracker.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
In-Reply-To: <0108521d-96ec-4ed9-9fb3-2183547ac13c@app.fastmail.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