Re: Memory leak on subquery as scalar operand

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com>, 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: 2023-02-22 19:43:00
Message-ID: 20230222194300.GF1653@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2023-02-22 21:24:14 Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
Previous Message Andres Freund 2023-02-22 19:23:50 Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash