Re: explain with costs in subselect.sql - Mailing list pgsql-hackers

From Tom Lane
Subject Re: explain with costs in subselect.sql
Date
Msg-id 32454.1520893542@sss.pgh.pa.us
Whole thread Raw
In response to explain with costs in subselect.sql  (Andres Freund <andres@anarazel.de>)
Responses Re: explain with costs in subselect.sql  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.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


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: explain with costs in subselect.sql
Next
From: Andres Freund
Date:
Subject: Re: explain with costs in subselect.sql