| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JIT compiling with LLVM v11 |
| Date: | 2018-03-12 19:25:06 |
| Message-ID: | 8fdf3e93-084f-c0cc-4ce6-fc213d713913@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/12/18 13:05, Andres Freund wrote:
>> will *not* use JIT, becaue jit_expressions applies at execution time.
> Right. It'd be easy to change that so jit_expressions=off wouldn't have
> an effect there anymore. But I'm not sure we want that? I don't have a
> strong feeling about this, except that I think jit_above_cost etc should
> apply at plan, not execution time.
I lean toward making everything apply at plan time. Not only is that
easier in the current code structure, but over time we'll probably want
to add more detailed planner knobs, e.g., perhaps an alternative
cpu_tuple_cost, and all of that would be a planner setting.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-12 19:55:23 | Re: [WIP PATCH] Index scan offset optimisation using visibility map |
| Previous Message | Stephen Frost | 2018-03-12 19:14:13 | Re: PATCH: Configurable file mode mask |