explain with costs in subselect.sql

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: explain with costs in subselect.sql
Date: 2018-03-12 22:20:23
Message-ID: 20180312222023.i4sgkbl4oqtstus3@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi Tom, all,

When forcing JITing to be enabled for all queries, obviously only useful
for testing, I noticed that two explain outputs changed after I added
explain support.

The only differences come from:

-- Unspecified-type literals in output columns should resolve as text

SELECT *, pg_typeof(f1) FROM
(SELECT 'foo' AS f1 FROM generate_series(1,3)) ss ORDER BY 1;

-- ... unless there's context to suggest differently

explain verbose select '42' union all select '43';
explain verbose select '42' union all select 43;

which don't use costs=off. Is there a reason for that? I assume it was
just a harmless oversight?

Has been added in


Andres Freund


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-03-12 22:25:42 Re: explain with costs in subselect.sql
Previous Message Tom Lane 2018-03-12 22:05:01 Re: [patch] BUG #15005: ANALYZE can make pg_class.reltuples inaccurate.