Horton

Re: BUG #15592: Memory overuse with subquery containing unnest() and set operations (11.x regression)

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

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-bugs@lists.postgresql.org, amdmi3@amdmi3.ru, Andrew Gierth <andrew@tao11.riddles.org.uk>, Jakub Janeček <jakub.janecek@comgate.cz>
Date: 2019-02-09T14:34:41Z
Lists: pgsql-bugs 
Andres Freund <andres@anarazel.de> writes:
>> ... Given that, I think it's ok
>> to not explicitly shutdown the expr context.

Uh, what?

> Dmitry, the fix will be included in the next minor release, which is
> scheduled for next week.

This doesn't really seem like the kind of patch to push on a release
weekend.  At this point you can't even be confident of getting a readout
from every active buildfarm member.

			regards, tom lane

Commits

  1. Plug leak in BuildTupleHashTable by creating ExprContext in correct context.

  2. simplehash: Add support for resetting a hashtable's contents.