Re: Memory leak on subquery as scalar operand

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, lauri(dot)laanmets(at)eesti(dot)ee, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Memory leak on subquery as scalar operand
Date: 2022-11-01 03:48:50
Message-ID: CAApHDvpL=3-61Lsfd9P5vuf48sJgKYP1qUULDEoKcAsEJpZA7g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 1 Nov 2022 at 13:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It's pretty odd though that it requires two
> sub-selects to cause the problem.

Perhaps that's just what it takes to bump the costs above the JIT threshold.

David

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-11-01 04:10:02 Re: Memory leak on subquery as scalar operand
Previous Message Tom Lane 2022-11-01 00:44:09 Re: Memory leak on subquery as scalar operand