Re: Change default of jit to off

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info>
Cc: Christoph Berg <myon(at)debian(dot)org>, Euler Taveira <euler(at)eulerto(dot)com>, Pierre Ducroquet <p(dot)psql(at)pinaraf(dot)info>, Jelte Fennema <postgres(at)jeltef(dot)nl>, Á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>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Michael Banck <mbanck(at)gmx(dot)net>
Subject: Re: Change default of jit to off
Date: 2026-02-03 17:03:51
Message-ID: CAKAnmmKZ_Yg2CEt9Wa-QZWZ7UePfWB9qnk=qDiXZcqNS5MdrGQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Given that so many places are already disabling it, +1 to disabling by
default - unless someone can come up with a costing tweak so it doesn't
fire when it shouldn't - but right now that seems something only humans can
truly determine.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message lakshmi 2026-02-03 17:07:58 Re: Proposal: Adding compression of temporary files
Previous Message Daniel Gustafsson 2026-02-03 16:58:22 Re: Changing the state of data checksums in a running cluster