| From: | James Coleman <jtc331(at)gmail(dot)com> |
|---|---|
| To: | Michael Banck <mbanck(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-25 19:21:24 |
| Message-ID: | CAAaqYe9qv0Juf8VJ47iQ1wZwUEO82pE+bULnJsGcSuNJRQ4E8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jun 25, 2023 at 5:10 AM Michael Banck <mbanck(at)gmx(dot)net> wrote:
>
> Hi,
>
> 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. Azure certainly does, but I don't
> have a Google Cloud SQL or RDS instance running right to verify their
> settings. I do seem to remember that they did as well though, at least a
> while back.
>
>
> Michael
I believe it's off by default in Aurora Postgres also.
Regards,
James Coleman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2023-06-25 20:35:47 | Re: Do we want a hashset type? |
| Previous Message | Tomas Vondra | 2023-06-25 18:56:30 | Re: Do we want a hashset type? |