public inbox for [email protected]help / color / mirror / Atom feed
does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 7+ messages / 5 participants [nested] [flat]
* does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 @ 2025-10-22 12:21 Ishan Arunkumar Joshi <[email protected]> 0 siblings, 1 reply; 7+ messages in thread From: Ishan Arunkumar Joshi @ 2025-10-22 12:21 UTC (permalink / raw) To: pgsql-admin Hi Team, 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. Error in PG v16.9 PostgreSQL Streaming Replication error while retrieving PostgreSQL logical log records: -1 : ERROR: invalid memory alloc request size 1803546384. The previous error occurred after scanning record 31, which has timeline+LSN+previousLSN 0+DD0A/2CBE4708+0/0 and timestamp 2025-07-09T12:13:04+07:00. Thanks & Regards, ------------------------- Ishan Joshi ________________________________ 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. ^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 @ 2025-10-22 14:26 Tom Lane <[email protected]> parent: Ishan Arunkumar Joshi <[email protected]> 0 siblings, 1 reply; 7+ messages in thread From: Tom Lane @ 2025-10-22 14:26 UTC (permalink / raw) To: Ishan Arunkumar Joshi <[email protected]>; +Cc: pgsql-admin 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">§</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 ^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 @ 2025-10-22 15:38 Álvaro Herrera <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 2 replies; 7+ messages in thread From: Álvaro Herrera @ 2025-10-22 15:38 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Ishan Arunkumar Joshi <[email protected]>; pgsql-admin On 2025-Oct-22, Tom Lane wrote: > 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. 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) ^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 @ 2025-10-22 15:53 Tom Lane <[email protected]> parent: Álvaro Herrera <[email protected]> 1 sibling, 1 reply; 7+ messages in thread From: Tom Lane @ 2025-10-22 15:53 UTC (permalink / raw) To: Álvaro Herrera <[email protected]>; +Cc: Ishan Arunkumar Joshi <[email protected]>; pgsql-admin =?utf-8?Q?=C3=81lvaro?= Herrera <[email protected]> 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 ^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 @ 2025-10-22 16:44 Ron Johnson <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 0 replies; 7+ messages in thread From: Ron Johnson @ 2025-10-22 16:44 UTC (permalink / raw) To: pgsql-admin On Wed, Oct 22, 2025 at 11:53 AM Tom Lane <[email protected]> wrote: > =?utf-8?Q?=C3=81lvaro?= Herrera <[email protected]> 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. > When there is, you can add it! -- Death to <Redacted>, and butter sauce. Don't boil me, I'm still alive. <Redacted> lobster! ^ permalink raw reply [nested|flat] 7+ messages in thread
* RE: does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 @ 2025-10-28 10:21 Ishan Arunkumar Joshi <[email protected]> parent: Álvaro Herrera <[email protected]> 1 sibling, 1 reply; 7+ messages in thread From: Ishan Arunkumar Joshi @ 2025-10-28 10:21 UTC (permalink / raw) To: Tom Lane <[email protected]>; pgsql-admin; +Cc: Álvaro Herrera <[email protected]> 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=d87d07b7ad3b782cb74566cd771ecdb2823ad... or https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=9f21be08e Thanks & Regards, ------------------------- Ishan Joshi -----Original Message----- From: Álvaro Herrera <[email protected]> Sent: Wednesday, October 22, 2025 9:08 PM To: Tom Lane <[email protected]> Cc: Ishan Arunkumar Joshi <[email protected]>; [email protected] 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 <[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. 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. ^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 @ 2025-10-28 10:22 Nolen Ngobeni <[email protected]> parent: Ishan Arunkumar Joshi <[email protected]> 0 siblings, 0 replies; 7+ messages in thread From: Nolen Ngobeni @ 2025-10-28 10:22 UTC (permalink / raw) To: Ishan Arunkumar Joshi <[email protected]>; +Cc: Tom Lane <[email protected]>; pgsql-admin; Álvaro Herrera <[email protected]> I need Assistant with the intergration On Tue, 28 Oct 2025, 12:21 Ishan Arunkumar Joshi, < [email protected]> 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=d87d07b7ad3b782cb74566cd771ecdb2823ad... > or > > https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=9f21be08e > > > Thanks & Regards, > ------------------------- > Ishan Joshi > > -----Original Message----- > From: Álvaro Herrera <[email protected]> > Sent: Wednesday, October 22, 2025 9:08 PM > To: Tom Lane <[email protected]> > Cc: Ishan Arunkumar Joshi <[email protected]>; > [email protected] > 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 <[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. > > 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. > ^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2025-10-28 10:22 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-10-22 12:21 does BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10 Ishan Arunkumar Joshi <[email protected]> 2025-10-22 14:26 ` Tom Lane <[email protected]> 2025-10-22 15:38 ` Álvaro Herrera <[email protected]> 2025-10-22 15:53 ` Tom Lane <[email protected]> 2025-10-22 16:44 ` Ron Johnson <[email protected]> 2025-10-28 10:21 ` Ishan Arunkumar Joshi <[email protected]> 2025-10-28 10:22 ` Nolen Ngobeni <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox