Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time

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>, maxim(dot)boguk(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
Date: 2023-03-28 03:20:30
Message-ID: 3386397.1679973630@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:
> I guess that means just add a check for EXEC_FLAG_EXPLAIN_ONLY in
> jit_compile_expr, or only set the es_jit_flags bits in
> standard_ExecutorStart() when not in EXEC_FLAG_EXPLAIN_ONLY. I'm not
> really sure which of those is better, but the attached does the former
> and seems to fix the issue.

Hmm, offhand I'd vote for the latter, because it adds cycles only
once per query not once per expression. But Andres may have a
better idea about how to do this.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Maxim Boguk 2023-03-28 04:54:04 Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
Previous Message David Rowley 2023-03-28 03:05:00 Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time