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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, amdmi3(at)amdmi3(dot)ru
Subject: Re: BUG #15592: Memory overuse with subquery containing unnest() and set operations (11.x regression)
Date: 2019-01-14 16:50:27
Message-ID: 27372.1547484627@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)anarazel(dot)de> writes:
> On January 14, 2019 8:24:40 AM PST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-01-14 16:57:55 Re: BUG #15592: Memory overuse with subquery containing unnest() and set operations (11.x regression)
Previous Message Andres Freund 2019-01-14 16:39:21 Re: BUG #15592: Memory overuse with subquery containing unnest() and set operations (11.x regression)