| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Pierre Ducroquet <p(dot)psql(at)pinaraf(dot)info> |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andreas Karlsson <andreas(at)proxel(dot)se>, Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Michael Banck <mbanck(at)gmx(dot)net>, Christoph Berg <myon(at)debian(dot)org> |
| Subject: | Re: Change default of jit to off |
| Date: | 2026-01-30 13:27:44 |
| Message-ID: | 674b350f5ae85b6b6fed36c9a1ecf5f12966abdb.camel@oopsware.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Freitag, dem 30.01.2026 um 12:28 +0100 schrieb Jelte Fennema-Nio:
> > People have also seen blog articles saying «JIT is bad, switch it
> > off» that are
> > right if you are in the wrong use cases for JIT. Which, to be fair,
> > is not
> > easy to figure out.
>
> +1 on disabling jit by default. At the FOSDEM Postgres developer
> meeting
> consensus was hugely in favor of changing the default. So attached is
> a
> trivial patch that does this.
+1, let's turn it off. I've seen many people hit by JIT and someone who
has the use case for it can easily turn it on again.
--
Thanks,
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jakub Wartak | 2026-01-30 13:43:41 | Re: pg_stat_io_histogram |
| Previous Message | Madyshev Egor | 2026-01-30 13:22:30 | RE: Idea to enhance pgbench by more modes to generate data (multi-TXNs, UNNEST, COPY BINARY) |