Horton
Menu

Re: Change default of jit to off

Bernd Helmle <mailings@oopsware.de>

View thread
From: Bernd Helmle <mailings@oopsware.de>
To: Jelte Fennema-Nio <postgres@jeltef.nl>, Pierre Ducroquet <p.psql@pinaraf.info>
Cc: Álvaro Herrera <alvherre@kurilemu.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andreas Karlsson <andreas@proxel.se>, Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Michael Banck <mbanck@gmx.net>, Christoph Berg <myon@debian.org>
Date: 2026-01-30T13:27:44Z
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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. jit: Change the default to off.