Re: JIT performance bug/regression & JIT EXPLAIN

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Maciek Sakrejda <m.sakrejda@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2020-01-27T19:02:26Z
Lists: pgsql-hackers
On Mon, Jan 27, 2020 at 12:41 PM Andres Freund <andres@anarazel.de> wrote:
> > I do not think that the readability-vs-usefulness tradeoff is going
> > to be all that good there, anyway.  Certainly for testing purposes
> > it's going to be more useful to examine portions of a structured output.
>
> I think I can live with that, I don't think it's going to be a very
> commonly used option. It's basically useful for regression tests, JIT
> improvements, and people that want to see whether they can change their
> query / schema to make better use of JIT - the latter category won't be
> many, I think.

I intensely dislike having information that we can't show in the text
format, or really, that we can't show in every format.

I might be outvoted, but I stand by that position.

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



Commits

  1. jit: Re-allow JIT compilation of execGrouping.c hashtable comparisons.

  2. Fix determination when slot types for upper executor nodes are fixed.