From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: lauri.laanmets@eesti.ee
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Memory leak on subquery as scalar operand
Date: Mon, 31 Oct 2022 20:44:09 -0400
Message-ID: <1046179.1667263449@sss.pgh.pa.us> (raw)
In-Reply-To: <CAApHDvrSbQkPUacnaonQzw1efFJM6HE5we-i9VVogBfEKGCCiA@mail.gmail.com>
References: <CAPH-tTxLf44s3CvUUtQpkDr1D8Hxqc2NGDzGXS1ODsfiJ6WSqA@mail.gmail.com>
<CAApHDvrSbQkPUacnaonQzw1efFJM6HE5we-i9VVogBfEKGCCiA@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, dgrowleyml@gmail.com, andres@anarazel.de, lauri.laanmets@eesti.ee, pgsql-bugs@lists.postgresql.org
Subject: Re: Memory leak on subquery as scalar operand
In-Reply-To: <1046179.1667263449@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox