public inbox for [email protected]  

help / color / mirror / Atom feed
From: Tom Lane <[email protected]>
To: Ishan Arunkumar Joshi <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
Date: Wed, 22 Oct 2025 10:26:33 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Ishan Arunkumar Joshi <[email protected]> writes:
> 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.

Our release notes don't usually mention bug numbers.  If you want to
track something that way, the best bet is to look at our git commit
log.  In this case the relevant log entry is (abbreviated a lot):

Author: Masahiko Sawada <[email protected]>
Branch: master Release: REL_18_BR [d87d07b7a] 2025-06-16 17:36:01 -0700
Branch: REL_17_STABLE Release: REL_17_6 [45c357e0e] 2025-06-16 17:35:58 -0700
Branch: REL_16_STABLE Release: REL_16_10 [b2ae07720] 2025-06-16 17:35:55 -0700
Branch: REL_15_STABLE Release: REL_15_14 [fc0fb77c5] 2025-06-16 17:35:53 -0700
Branch: REL_14_STABLE Release: REL_14_19 [983b36362] 2025-06-16 17:35:50 -0700
Branch: REL_13_STABLE Release: REL_13_22 [1230be12f] 2025-06-16 17:35:48 -0700

    Fix re-distributing previously distributed invalidation messages during logical decoding.
    ...
    Bug: #18938 #18942
    ...
    Discussion: https://postgr.es/m/[email protected]
    Discussion: https://postgr.es/m/[email protected]
    Discussion: https://postgr.es/m/[email protected]
    Discussion: https://postgr.es/m/CAD1FGCT2sYrP_70RTuo56QTizyc+J3wJdtn2gtO3VttQFpdMZg@mail.gmail.com
    Discussion: https://postgr.es/m/CANO2=B=2BT1hSYCE=nuuTnVTnjidMg0+-FfnRnqM6kd23qoygg@mail.gmail.com
    Backpatch-through: 13

and the corresponding entry in the v16.10 release notes is

    <listitem>
<!--
Author: Masahiko Sawada <[email protected]>
Branch: master Release: REL_18_BR [d87d07b7a] 2025-06-16 17:36:01 -0700
Branch: REL_17_STABLE [45c357e0e] 2025-06-16 17:35:58 -0700
Branch: REL_16_STABLE [b2ae07720] 2025-06-16 17:35:55 -0700
Branch: REL_15_STABLE [fc0fb77c5] 2025-06-16 17:35:53 -0700
Branch: REL_14_STABLE [983b36362] 2025-06-16 17:35:50 -0700
Branch: REL_13_STABLE [1230be12f] 2025-06-16 17:35:48 -0700
Branch: REL_13_STABLE [87819f766] 2025-06-24 07:07:40 -0700
-->
     <para>
      Avoid re-distributing cache invalidation messages from other
      transactions during logical replication (vignesh C)
      <ulink url="&commit_baseurl;b2ae07720">&sect;</ulink>
     </para>

     <para>
      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.
     </para>
    </listitem>


I'm not really sure why the references to "logical replication" and
"memory allocation failure" weren't enough to clue you in that
this was probably the fix you wanted.  Also, if you did see that
but weren't sure, you could have followed the commit link and
found the commit message that way.

			regards, tom lane





reply
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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox