Re: explain with costs in subselect.sql

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

Andres Freund <andres(at)anarazel(dot)de> writes:
> 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?

Duh, yeah, explain (verbose, costs off) would do fine there.
Mea culpa. Do you want to fix it?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-03-12 22:28:07 Re: explain with costs in subselect.sql
Previous Message Andres Freund 2018-03-12 22:20:23 explain with costs in subselect.sql