Re: Change default of jit to off - Mailing list pgsql-hackers

From Pierre Ducroquet
Subject Re: Change default of jit to off
Date
Msg-id gPNlX1QTDtJW2Cyi3fA2OGFvoIybkehUYKCHCe2r3Ujm_0y9V1T13CPI2MA6RyPhLi8zNwNczq1DNrbh1l47eVn6tOwz-qzG2yXw_XtptTQ=@pinaraf.info
Whole thread
In response to Re: Change default of jit to off  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Change default of jit to off
List pgsql-hackers
Le vendredi 20 mars 2026 à 5:25 PM, Tom Lane <tgl@sss.pgh.pa.us> a écrit :

> Tomas Vondra <tomas@vondra.me> writes:
> > ISTM there's a clear consensus to get this committed for PG19, so
> > barring objections I'll take care of that in the next couple days.
> > Unless someone else wants to ...
>
> +1
>
> > Another option would be to leave that for mid-beta, which is where we
> > tweaked the io_method GUCs last year. But we did that to get some
> > testing for 'worker' (in case we revert to 'sync'), and we don't need
> > that for jit.
>
> Doesn't seem like something to change mid-beta.  If it makes anyone
> unhappy, we'd best find out sooner not later.

I've not seen any feedback on my "counter"-proposal: switch jit_tuple_deforming to off by default. Sure, for the
perfectllvmjit use cases this will reduce the performance benefits, but it will remove most if not all the problematic
queries(for instance queries running on many partitions, adding/moving columns leading to explosions in compilation
time...)
Of course if there are other troublesome situations, I would love being proven wrong.



pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: Bug in pg_get_aios()
Next
From: John Naylor
Date:
Subject: Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?