From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: maxim.boguk@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
Date: Mon, 27 Mar 2023 17:38:19 -0400
Message-ID: <3348298.1679953099@sss.pgh.pa.us> (raw)
In-Reply-To: <20230327212830.dpp2u47je5ozf5q7@awork3.anarazel.de>
References: <17871-16521a70c16cb83c@postgresql.org>
<20230327212830.dpp2u47je5ozf5q7@awork3.anarazel.de>
Andres Freund <andres@anarazel.de> writes:
> On 2023-03-27 08:04:59 +0000, PG Bug reporting form wrote:
>> postgresql_fdw remote estimated explain calls could trigger JIT compilation
>> on the remote side (why explain without analyze trying use JIT at all???),
>> and with partitioned tables it will lead to very slow planning.
> It should not trigger all of JIT, just generating the bitcode, but not
> optimizing / emitting it.
I was wondering if we could skip doing even that much when
EXEC_FLAG_EXPLAIN_ONLY is set. Without a test case, though,
I'm not very sure where the jitter is getting reached.
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, andres@anarazel.de, maxim.boguk@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
In-Reply-To: <3348298.1679953099@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