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

From Justin Pryzby
Subject Re: Memory leak on subquery as scalar operand
Date
Msg-id 20230222194300.GF1653@telsasoft.com
Whole thread Raw
In response to Re: Memory leak on subquery as scalar operand  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
On Mon, Oct 31, 2022 at 10:51:32PM -0700, Andres Freund wrote:
> Hi,
> 
> On 2022-11-01 00:52:16 -0400, Tom Lane wrote:
> > David Rowley <dgrowleyml@gmail.com> writes:
> > > The single subquery version also crashes for me, so perhaps it's just
> > > the amount of memory that's being used and when the OOM killer is
> > > triggering.
> > > It crashes even when I set jit_inline_above_cost and
> > > jit_optimize_above_cost above the query's cost.
> > 
> > Hmm, maybe we're not seeing the same thing?
> 
> I can't reproduce that either.

@David: does the query really crash as you described - with neither jit
inlining nor optimization ?

Is it due to OOM or something else ?
Does it crash with/without Andres' patches ?
What version were you testing ?

-- 
Justin



pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
Next
From: Tom Lane
Date:
Subject: Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash