Re: BUG #15592: Memory overuse with subquery containing unnest() and set operations (11.x regression)
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-bugs@lists.postgresql.org, amdmi3@amdmi3.ru
Date: 2019-01-14T16:50:27Z
Lists: pgsql-bugs
Andres Freund <andres@anarazel.de> writes: > On January 14, 2019 8:24:40 AM PST, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Ugh. Something is creating ExprContexts and not freeing them --- a >> memory context dump taken at ExecutorEnd shows > Think I know where the problem is - let me have a coffee and check? I think I might have a good lying around... I had just determined that the extra context was added by bf6c614a2, which at this point has accumulated a pretty serious collection of bugs, judging by subsequent mentions in the commit log. I'm inclined to think that entire patch needs review. regards, tom lane
Commits
-
Plug leak in BuildTupleHashTable by creating ExprContext in correct context.
- 9cf37a527cf8 11.2 landed
- 5567d12ce030 12.0 landed
-
simplehash: Add support for resetting a hashtable's contents.
- 350b0a40375e 11.2 landed
- 3b632a58e798 12.0 landed