Re: Add missing JIT inline pass for llvm>=17
Michael Banck <mbanck@gmx.net>
From: Michael Banck <mbanck@gmx.net>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Andreas Karlsson <andreas@proxel.se>, Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2026-01-16T09:29:59Z
Lists: pgsql-hackers
Hi, On Thu, Jan 15, 2026 at 12:26:23PM +0100, Álvaro Herrera wrote: > On 2026-Jan-15, Andreas Karlsson wrote: > > Great find! Sadly shows how little people actually use JIT. > > I disagree. Given that JIT is enabled by default, I think lots of > people use it. Well, not sure about that - all of the three major hyperscalers disable JIT in their managed Postgres offerings (or at least used to when I last checked), and those are a major chunk of usage these days. Also, both the RPM and (since recently) the Debian/Ubuntu community packages have factored out the LLVM/jit part into their own packages and AFAIK they do not get installed by default. So while the GUC is on by default, a lot of users might not use JIT these days and not know either way. > What they don't do, is realize that things are slower > than they could be -- much less try to figure out why. Right. Michael
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
jit: Add missing inline pass for LLVM >= 17.
- f1c6b153cabd 18.2 landed
- d0bb0e5b364f 17.8 landed
- 7600dc79c231 16.12 landed
- cbdd09ae1b57 15.16 landed
- de8081c30e5a 14.21 landed
- e5d99b4d9ef4 19 (unreleased) landed