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 1lr091-0004aO-UU for pgsql-hackers@arkaria.postgresql.org; Wed, 09 Jun 2021 15:29:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lr090-0007Xb-RI for pgsql-hackers@arkaria.postgresql.org; Wed, 09 Jun 2021 15:29:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lr090-0007XL-2H for pgsql-hackers@lists.postgresql.org; Wed, 09 Jun 2021 15:29:26 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lr08x-0004lS-V4 for pgsql-hackers@lists.postgresql.org; Wed, 09 Jun 2021 15:29:25 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id ACF92275E; Wed, 9 Jun 2021 11:29:21 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 09 Jun 2021 11:29:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=mdKLV7VniIQaR23tlg2JnxdUNndLdHGtx03t/FuSI8s=; b=pGnEeves clGFc4J1rJOEEkCTUOJbCAgTBKW/t6udI+0Ul7q8lQjsHr/G8a1r3e8rMmRw49KF iJE5zx9qvzF2Xvr+Pmkwntfoqq54hNIrnLfW/fMHYzkBn3PwKDaVtbzLr1T0ldM4 Q9XdJvCSu6CLUb3kMu2gbY583PVAn3NnOFuNG7/62UbJTiEGxD/qzR+AYhjwBQG7 l2YjD8NDM34jh+JQQd9KocH/s1Jyp1Cm45iAkuFJFIrLYUgLHrAEyWyBUs6jxo4J pC0jdlDFEWcnJeVLs1RsOxOQEJdlOoW4hXECYrUvCnTeWVfjzHPmwpDHFq8hxoQ1 MIsTpa01x7h/DA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeduuddgledtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggugfgjsehtkeertddttddunecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpeeggeevveffveejffdutefhvddtgeeghffhgfeuhfefjeei gfevhfefleevtdduteenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 9 Jun 2021 11:29:20 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 928802A0A4D; Wed, 9 Jun 2021 11:29:17 -0400 (-04) Date: Wed, 9 Jun 2021 11:29:17 -0400 From: Alvaro Herrera To: Dilip Kumar Cc: Amit Kapila , Andres Freund , Ashutosh Bapat , Peter Eisentraut , Petr Jelinek , PostgreSQL Hackers , Tomas Vondra Subject: Re: Decoding speculative insert with toast leaks memory Message-ID: <202106091529.d24gsfbiaeut@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk May I suggest to use a different name in the blurt_and_lock_123() function, so that it doesn't conflict with the one in insert-conflict-specconflict? Thanks -- Álvaro Herrera 39°49'30"S 73°17'W