| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Michael Banck <mbanck(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | James Coleman <jtc331(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, David Pirotte <dpirotte(at)gmail(dot)com> |
| Subject: | Re: Stampede of the JIT compilers |
| Date: | 2023-06-26 11:10:50 |
| Message-ID: | 3a8af5ebfb414f35a4015366e11eefd59d167a8e.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 2023-06-25 at 11:10 +0200, Michael Banck wrote:
> On Sat, Jun 24, 2023 at 01:54:53PM -0400, Tom Lane wrote:
> > I don't know whether raising the default would be enough to fix that
> > in a nice way, and I certainly don't pretend to have a specific value
> > to offer. But it's undeniable that we have a serious problem here,
> > to the point where JIT is a net negative for quite a few people.
>
> Some further data: to my knowledge, most major managed postgres
> providers disable jit for their users.
I have also started recommending jit=off for all but analytic workloads.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2023-06-26 11:20:00 | function arguments are not PG_FUNCTION_ARGS, how to pass Node *escontext |
| Previous Message | jian he | 2023-06-26 11:06:21 | Re: Do we want a hashset type? |