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 1ktvbJ-0000Cz-87 for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Dec 2020 16:42:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ktvbH-0007W9-QH for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Dec 2020 16:42:27 +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 1ktvbH-0007W1-Jb for pgsql-hackers@lists.postgresql.org; Mon, 28 Dec 2020 16:42:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ktvbF-00079u-Ih for pgsql-hackers@postgresql.org; Mon, 28 Dec 2020 16:42:27 +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 0BSGgMmi1669880; Mon, 28 Dec 2020 11:42:23 -0500 From: Tom Lane To: Peter Eisentraut cc: pgsql-hackers Subject: Re: pgsql: Fix memory leak in plpgsql's CALL processing. In-reply-to: <1598242.1609168300@sss.pgh.pa.us> References: <1598242.1609168300@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Mon, 28 Dec 2020 10:11:40 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1669878.1609173742.1@sss.pgh.pa.us> Date: Mon, 28 Dec 2020 11:42:22 -0500 Message-ID: <1669879.1609173742@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > so it looks like a memory clobber --- probably some data structure is > being built in the wrong memory context. Will look closer shortly. Brain-dead typo ... where's my brown paper bag? regards, tom lane