Обсуждение: does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10

 

---

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.  

Ishan Arunkumar Joshi <ishan.joshi@netcracker.com> writes:
> 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. 

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 <msawada@postgresql.org>
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/680bdaf6-f7d1-4536-b580-05c2760c67c6@deepbluecap.com
    Discussion: https://postgr.es/m/18942-0ab1e5ae156613ad@postgresql.org
    Discussion: https://postgr.es/m/18938-57c9a1c463b68ce0@postgresql.org
    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 <msawada@postgresql.org>
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">§</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

On 2025-Oct-22, Tom Lane wrote:

> Ishan Arunkumar Joshi <ishan.joshi@netcracker.com> 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.

Maybe we should add that.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
Thou shalt check the array bounds of all strings (indeed, all arrays), for
surely where thou typest "foo" someone someday shall type
"supercalifragilisticexpialidocious" (5th Commandment for C programmers)

=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de> writes:
> On 2025-Oct-22, Tom Lane wrote:
>> Our release notes don't usually mention bug numbers.

> Maybe we should add that.

I don't think so, because as often as not there is no bug number.

            regards, tom lane

Hi Tom,

Thanks for the confirmation.

can we get the commit changes for " Branch: REL_16_STABLE Release: REL_16_10 [b2ae07720] 2025-06-16 17:35:55 -0700"

I tried to get details of changes as we need to change the same in v16.9.

is that the same as below
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=d87d07b7ad3b782cb74566cd771ecdb2823adf6a
or
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=9f21be08e


Thanks & Regards,
-------------------------
Ishan Joshi

-----Original Message-----
From: Álvaro Herrera <alvherre@kurilemu.de>
Sent: Wednesday, October 22, 2025 9:08 PM
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ishan Arunkumar Joshi <ishan.joshi@netcracker.com>; pgsql-admin@postgresql.org
Subject: Re: does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10

[External Email]
________________________________



On 2025-Oct-22, Tom Lane wrote:

> Ishan Arunkumar Joshi <ishan.joshi@netcracker.com> 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.

Maybe we should add that.

--
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest "foo" someone
somedayshall type "supercalifragilisticexpialidocious" (5th Commandment for C programmers)
 


________________________________
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
takingof 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.