| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JIT compiling with LLVM v11 |
| Date: | 2018-03-12 21:19:43 |
| Message-ID: | 20180312211943.oyurpjxbq3pgabun@alap3.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-03-12 17:14:00 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > Currently a handful of explain outputs in the regression tests change
> > output when compiled with JITing. Therefore I'm thinking of adding
> > JITINFO or such option, which can be set to false for those tests?
> > Maintaining duplicate output for them seems painful. Better ideas?
>
> Why not just suppress that info when COSTS OFF is specified?
I wondered about that too. But that'd mean it'd be harder to write a
test that tests the planning bits of JITing (i.e. decision whether to
use optimization & inlining or not) . Not sure if it's worth adding
complexity to be able to do so.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mat Arye | 2018-03-12 21:27:01 | Re: Additional Statistics Hooks |
| Previous Message | Tom Lane | 2018-03-12 21:14:00 | Re: JIT compiling with LLVM v11 |