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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2020-12-28T16:42:22Z

Lists: 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

Commits

Further fix thinko in plpgsql memory leak fix.
- 7966b41ded75 11.11 landed
- d37965965ad3 12.6 landed
- 63d78d106d2f 13.2 landed
- 5f2e09bcccd7 14.0 landed
Fix thinko in plpgsql memory leak fix.
- fd1347f9d8de 12.6 landed
- ea80d8d9437e 14.0 landed
- 2e15f48d9727 11.11 landed
- 0ea25ed108d8 13.2 landed
Fix memory leak in plpgsql's CALL processing.
- a6b1f5365d58 14.0 cited