| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JIT performance bug/regression & JIT EXPLAIN |
| Date: | 2020-01-27 21:18:33 |
| Message-ID: | 20518.1580159913@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maciek Sakrejda | 2020-01-27 21:31:06 | Re: JIT performance bug/regression & JIT EXPLAIN |
| Previous Message | Alvaro Herrera | 2020-01-27 21:06:27 | Re: standby apply lag on inactive servers |