| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Default JIT setting in V12 |
| Date: | 2019-09-16 15:12:04 |
| Message-ID: | CAMkU=1x-hjo3cszwRG9PV=AvQzcmJ-+mQGqQVTbjoVmtEV4azg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 4, 2019 at 11:24 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On 2019-09-04 07:51:16 -0700, Andres Freund wrote:
>
> Or better, something slightly more complete, like the attached (which
> affects both code-gen time optimizations (which are more like peephole
> ones), and both function/global ones that are cheap).
>
Yes, that does completely solve the issue I raised. It makes JIT either
better or at least harmless, even when falling into the gap between
jit_above_cost
and jit_optimize_above_cost.
What TPC-H implementation do you use/recommend? This one
https://wiki.postgresql.org/wiki/DBT-3?
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-09-16 15:20:08 | Re: Define jsonpath functions as stable |
| Previous Message | Kuntal Ghosh | 2019-09-16 15:08:58 | Re: POC: Cleaning up orphaned files using undo logs |