Re: pgsql: Fix memory leak in plpgsql's CALL processing.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Fix memory leak in plpgsql's CALL processing.
Date: 2020-12-28 16:42:22
Message-ID: 1669879.1609173742@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2020-12-28 16:56:08 pgsql: Further fix thinko in plpgsql memory leak fix.
Previous Message Tom Lane 2020-12-28 16:41:39 pgsql: Fix thinko in plpgsql memory leak fix.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-12-28 18:25:14 Re: Better client reporting for "immediate stop" shutdowns
Previous Message Bruce Momjian 2020-12-28 15:39:51 Re: pgsql: Add pg_alterckey utility to change the cluster key