Postgres Pro
Downloads
Home   >   mailing lists

Re: Memory leak on subquery as scalar operand - Mailing list pgsql-bugs

From David Rowley
Subject Re: Memory leak on subquery as scalar operand
Date
Msg-id CAApHDvpL=3-61Lsfd9P5vuf48sJgKYP1qUULDEoKcAsEJpZA7g@mail.gmail.com
Whole thread Raw
In response to Re: Memory leak on subquery as scalar operand  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Memory leak on subquery as scalar operand  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 
On Tue, 1 Nov 2022 at 13:44, Tom Lane <tgl@sss.pgh.pa.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Memory leak on subquery as scalar operand
Next
From: Tom Lane
Date:
Subject: Re: Memory leak on subquery as scalar operand