Re: Memory leak on subquery as scalar operand

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
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 00:44:09
Message-ID: 1046179.1667263449@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

David Rowley <dgrowleyml(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2022-11-01 03:48:50 Re: Memory leak on subquery as scalar operand
Previous Message David Rowley 2022-10-31 23:20:38 Re: Memory leak on subquery as scalar operand