| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: bad JIT decision |
| Date: | 2020-07-24 22:42:56 |
| Message-ID: | CAApHDvoFsWpkwt+pKuuswChC+6EKQO+FfwicTQpSfTXAHDfoZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, 25 Jul 2020 at 10:37, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > However, for now, you might just want to try raising various jit
> > thresholds so that it only is enabled for more expensive plans.
>
> Yeah. I'm fairly convinced that the v12 defaults are far too low,
> because we are constantly seeing complaints of this sort.
I think plan cost overestimation is a common cause of unwanted jit too.
It would be good to see the EXPLAIN ANALYZE so we knew if that was the
case here.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2020-07-24 22:46:35 | Re: bad JIT decision |
| Previous Message | Tom Lane | 2020-07-24 22:37:02 | Re: bad JIT decision |