Re: Change default of jit to off

From: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
To: Bernd Helmle <mailings(at)oopsware(dot)de>
Cc: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Pierre Ducroquet <p(dot)psql(at)pinaraf(dot)info>, Á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-31 03:02:47
Message-ID: CAGjGUA+WYmXLHb5=DDKi5NPY+nGJ96dB=9xSTkzuc7gxSJYwuQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Agree +1,Open it again if necessary.

On Fri, 30 Jan 2026 at 21:27, Bernd Helmle <mailings(at)oopsware(dot)de> wrote:

> 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
>
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2026-01-31 03:44:55 Re: More speedups for tuple deformation
Previous Message John Naylor 2026-01-31 02:47:49 Re: More speedups for tuple deformation