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

From Tom Lane
Subject Re: JIT performance bug/regression & JIT EXPLAIN
Date
Msg-id 20518.1580159913@sss.pgh.pa.us
Whole thread Raw
In response to Re: JIT performance bug/regression & JIT EXPLAIN  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: JIT performance bug/regression & JIT EXPLAIN
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
>>> 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 intensely dislike having information that we can't show in the text
> format, or really, that we can't show in every format.

Well, if it's relegated to a "jit = detail" option or some such,
the readability objection could be overcome.  But I'm still not clear
on how you'd physically wedge it into the output, at least not in a way
that matches up with the proposal that non-text modes handle this stuff
by producing sub-nodes for the existing types of expression fields.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: standby apply lag on inactive servers
Next
From: Maciek Sakrejda
Date:
Subject: Re: JIT performance bug/regression & JIT EXPLAIN