Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uYR2U-006Fss-Dg for pgsql-general@arkaria.postgresql.org; Sun, 06 Jul 2025 15:12:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uYR2S-00Dxga-FU for pgsql-general@arkaria.postgresql.org; Sun, 06 Jul 2025 15:12:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uYR2S-00DxgC-56 for pgsql-general@lists.postgresql.org; Sun, 06 Jul 2025 15:12:20 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uYR2Q-0064bL-0t for pgsql-general@postgresql.org; Sun, 06 Jul 2025 15:12:20 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 566FCEsQ199125; Sun, 6 Jul 2025 11:12:14 -0400 From: Tom Lane To: Soni M cc: pgsql-general@postgresql.org Subject: Re: Logical Replication 08P01 invalid memory alloc request size 1095736448 In-reply-to: References: Comments: In-reply-to Soni M message dated "Sun, 06 Jul 2025 16:40:55 +0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <199123.1751814734.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 06 Jul 2025 11:12:14 -0400 Message-ID: <199124.1751814734@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Soni M writes: > We just do patch updates from 15.12 to 15.13, restart Logical Master and > then Logical Replica, and suddenly Logical replication stops working. > Streaming replication of both are fine. This sounds like the same bug previously discussed in https://www.postgresql.org/message-id/flat/680bdaf6-f7d1-4536-b580-05c2760= c67c6%40deepbluecap.com We'll have a fix in next month's quarterly releases. For the moment, you could either roll back to 15.12 or cherry-pick the fix at commit fc0fb77c5. regards, tom lane