| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 19:02:26 |
| Message-ID: | CA+TgmobX1h+KfGNWZ+egausdZy2OcX7yZm_Bw5X+FSQTnwMwqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 27, 2020 at 12:41 PM Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-01-27 19:26:42 | Re: our checks for read-only queries are not great |
| Previous Message | Mahendra Singh Thalor | 2020-01-27 19:02:16 | Re: making the backend's json parser work in frontend code |