Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1iwBmQ-0006um-EL
	for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Jan 2020 21:18:46 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1iwBmO-00053i-Vn
	for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Jan 2020 21:18:44 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1iwBmO-00053b-M4
	for pgsql-hackers@lists.postgresql.org; Mon, 27 Jan 2020 21:18:44 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1iwBmH-0004mM-Rq
	for pgsql-hackers@postgresql.org; Mon, 27 Jan 2020 21:18:44 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 00RLIXAb020519;
	Mon, 27 Jan 2020 16:18:33 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
cc: Andres Freund <andres@anarazel.de>,
 Maciek Sakrejda <m.sakrejda@gmail.com>,
        "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: JIT performance bug/regression & JIT EXPLAIN
In-reply-to: 
 <CA+TgmobX1h+KfGNWZ+egausdZy2OcX7yZm_Bw5X+FSQTnwMwqg@mail.gmail.com>
References: <20190927072053.njf6prdl3vb7y7qb@alap3.anarazel.de>
 <CA+TgmoZQ1691Mdp6_49nmmpRw7h5Z5CPDB5uD5CHVj1-fkSvsA@mail.gmail.com>
 <20191028232145.oj6jw3vnisikm7nl@alap3.anarazel.de>
 <CA+TgmoYXTchjLctjovKdWuqx+AhN0=D8qdRZT0YDc6s2rwrFfw@mail.gmail.com>
 <20191113200318.glenebxhlcu6crtr@alap3.anarazel.de>
 <CA+TgmoZb=U4m4pxXQ3Qj=dwMaJjq7omAKN3hPYfsRuWU+aY+DQ@mail.gmail.com>
 <CAOtHd0AtNzMhcBdf-rZyeHSYehwHUnAr4ULfHNwZhPv9o9gELw@mail.gmail.com>
 <18465.1580145353@sss.pgh.pa.us>
 <20200127174103.i4nxrzromqk24pfn@alap3.anarazel.de>
 <CA+TgmobX1h+KfGNWZ+egausdZy2OcX7yZm_Bw5X+FSQTnwMwqg@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Mon, 27 Jan 2020 14:02:26 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20517.1580159913.1@sss.pgh.pa.us>
Date: Mon, 27 Jan 2020 16:18:33 -0500
Message-ID: <20518.1580159913@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

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