Re: does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10

I need Assistant with the intergration

On Tue, 28 Oct 2025, 12:21 Ishan Arunkumar Joshi, <
ishan(dot)joshi(at)netcracker(dot)com> wrote:

> 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(at)kurilemu(dot)de>
> Sent: Wednesday, October 22, 2025 9:08 PM
> To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Cc: Ishan Arunkumar Joshi <ishan(dot)joshi(at)netcracker(dot)com>;
> pgsql-admin(at)postgresql(dot)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(dot)joshi(at)netcracker(dot)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)
>
>
> ________________________________
> 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.
>