Re: JIT compiling with LLVM v11

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: JIT compiling with LLVM v11
Date: 2018-03-13 18:30:56
Message-ID: 20180313183056.inval7jnzbewdf27@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018-03-13 10:25:49 -0400, Peter Eisentraut wrote:
> On 3/12/18 17:04, Andres Freund wrote:
> > │ JIT: │
> > │ Functions: 4 │
> > │ Inlining: false │
> > │ Inlining Time: 0.000 │
> > │ Optimization: false │
> > │ Optimization Time: 5.023 │
> > │ Emission Time: 34.987 │
>
> The time quantities need some units.
>
> > │ Execution time: 46.277 ms │
>
> like this :)

Yea, I know. I was planning to start a thread about that. explain.c is
littered with code like
if (es->format == EXPLAIN_FORMAT_TEXT)
appendStringInfo(es->str, "Planning time: %.3f ms\n",
1000.0 * plantime);
else
ExplainPropertyFloat("Planning Time", 1000.0 * plantime, 3, es);
which, to me, is bonkers. I think we should add add 'const char *unit'
parameter to at least ExplainProperty{Float,Integer,Long}? Or a *Unit
version of them doing so, allowing a bit more gradual change?

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-03-13 18:31:40 Re: [HACKERS] why not parallel seq scan for slow functions
Previous Message Andres Freund 2018-03-13 18:27:22 Re: TupleTableSlot abstraction