Re: JIT performance bug/regression & JIT EXPLAIN - Mailing list pgsql-hackers

From Robert Haas
Subject Re: JIT performance bug/regression & JIT EXPLAIN
Date
Msg-id CA+TgmobX1h+KfGNWZ+egausdZy2OcX7yZm_Bw5X+FSQTnwMwqg@mail.gmail.com
Whole thread Raw
In response to Re: JIT performance bug/regression & JIT EXPLAIN  (Andres Freund <andres@anarazel.de>)
Responses Re: JIT performance bug/regression & JIT EXPLAIN
List 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



pgsql-hackers by date:

Previous
From: Mahendra Singh Thalor
Date:
Subject: Re: making the backend's json parser work in frontend code
Next
From: Stephen Frost
Date:
Subject: Re: our checks for read-only queries are not great