From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: pgsql: Fix memory leak in plpgsql's CALL processing.
Date: Mon, 28 Dec 2020 11:42:22 -0500
Message-ID: <1669879.1609173742@sss.pgh.pa.us> (raw)
In-Reply-To: <1598242.1609168300@sss.pgh.pa.us>
References: <E1kNHOx-0003xj-TX@gemulon.postgresql.org>
<f075f7be-c654-9aa8-3ffc-e9214622f02a@enterprisedb.com>
<1598242.1609168300@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter.eisentraut@enterprisedb.com, pgsql-hackers@postgresql.org
Subject: Re: pgsql: Fix memory leak in plpgsql's CALL processing.
In-Reply-To: <1669879.1609173742@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox