Re: JIT performance bug/regression & JIT EXPLAIN

On Fri, Sep 27, 2019 at 3:21 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> - JIT-Expr: whether the expression was JIT compiled (might e.g. not be
> the case because no parent was provided)
> - JIT-Deform-{Scan,Outer,Inner}: wether necessary, and whether JIT accelerated.
>
> I don't like these names much, but ...
>
> For the deform cases I chose to display
> a) the function name if JIT compiled
> b) "false" if the expression is JIT compiled, deforming is
> necessary, but deforming is not JIT compiled (e.g. because the slot type
> wasn't fixed)
> c) "null" if not necessary, with that being omitted in text mode.

I mean, why not just omit in all modes if it's not necessary? I don't
see that making the information we produce randomly inconsistent
between modes is buying us anything.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company