Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qDQlp-0000XQ-P1 for pgsql-admin@arkaria.postgresql.org; Sun, 25 Jun 2023 14:31:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qDQlo-0000ye-Ku for pgsql-admin@arkaria.postgresql.org; Sun, 25 Jun 2023 14:31:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qDQlo-0000yN-9Q for pgsql-admin@lists.postgresql.org; Sun, 25 Jun 2023 14:31:16 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qDQll-000PBV-CE for pgsql-admin@lists.postgresql.org; Sun, 25 Jun 2023 14:31:15 +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 35PEVALB509158; Sun, 25 Jun 2023 10:31:10 -0400 From: Tom Lane To: ROHIT SACHDEVA cc: pgsql-admin@lists.postgresql.org Subject: Re: Fix buffer refcount leak with FDW bulk inserts In-reply-to: References: Comments: In-reply-to ROHIT SACHDEVA message dated "Sun, 25 Jun 2023 14:21:28 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <509156.1687703470.1@sss.pgh.pa.us> Date: Sun, 25 Jun 2023 10:31:10 -0400 Message-ID: <509157.1687703470@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ROHIT SACHDEVA writes: > When i am try to increase the batch_size parameter and do the insertion > part i received this error. > WARNING: buffer refcount leak: [1733373] (rel=base/19360/251000, > blockNum=809 That's just a warning, not an error. It's pretty harmless. > What is the impact of this error should I perform the insertion again. No. What you should do is update to the current minor release (14.8), which contains a fix for a bug matching this symptom. (If you can still reproduce the warning on 14.8, we'd be interested to see a self-contained test case.) regards, tom lane