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

From Tom Lane
Subject Re: Memory leak on subquery as scalar operand
Date
Msg-id 1046179.1667263449@sss.pgh.pa.us
Whole thread Raw
In response to Re: Memory leak on subquery as scalar operand  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Memory leak on subquery as scalar operand  (David Rowley <dgrowleyml@gmail.com>)
Re: Memory leak on subquery as scalar operand  (Lauri Laanmets <pcspets@gmail.com>)
List pgsql-bugs
David Rowley <dgrowleyml@gmail.com> writes:
> Does it still OOM if you do:
> SET jit TO off; ?

Ah, bingo --- I can reproduce the behavior if I use a JIT-enabled
build.  So this is related to the known problems with leakage of
compiled objects.  It's pretty odd though that it requires two
sub-selects to cause the problem.

            regards, tom lane



pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: Memory leak on subquery as scalar operand
Next
From: David Rowley
Date:
Subject: Re: Memory leak on subquery as scalar operand