Re: Add parameter jit_warn_above_fraction - Mailing list pgsql-hackers

From David Rowley
Subject Re: Add parameter jit_warn_above_fraction
Date
Msg-id CAApHDvov2Zknd6KOT07YBOG1qGd4DCapAJ48gpa0161R7Sbc_g@mail.gmail.com
Whole thread Raw
In response to Re: Add parameter jit_warn_above_fraction  (Andres Freund <andres@anarazel.de>)
Responses Re: Add parameter jit_warn_above_fraction  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Add parameter jit_warn_above_fraction  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Wed, 30 Mar 2022 at 12:16, Andres Freund <andres@anarazel.de> wrote:
> > I did propose a patch to address this in [1]. It does need more work
> > and I do plan to come back to it for v16.
>
> FWIW, that doesn't seem quite right - won't it stop JITing e.g. on the inner
> side of a nested loop, just because it's cheap, even though that's where the
> bulk of the benefits comes from?

Yeah, I think the total cost would need to be multiplied by the number
of times we expect to call that part of the plan.  I've not yet sat
down to figure out if that's easy/cheap or hard/costly information to
obtain.

David



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
Next
From: Andres Freund
Date:
Subject: Re: pg_stat_reset_single_*_counters vs pg_stat_database.stats_reset