On Tue, Aug 24, 2010 at 1:21 PM, Tom Lane <[email protected]> wrote: > Greg Stark <[email protected]> writes: >> On Tue, Aug 24, 2010 at 5:06 PM, Tom Lane <[email protected]> wrote: >>> Function Scan on pg_catalog.unnest f (cost=0.00..1.50 rows=100 width=96) >>> Output: (((lv)::text || op) || (rv)::text) >>> Function Call: unnest(ARRAY[ROW(('1.2.2'::text)::semver, '='::text, >>> ('1.2.2'::text)::semver), ROW('1.2.23', '=', '1.2.23')]) > >> This may be the ultimate bike-shed but Wouldn't this be clearer the >> other way around? I generally think input comes first and then output. > > The order was bothering me a bit too, but there's a generic decision > in there that the tlist is shown before any node-type-specific items. > Not sure that we want to move it to the bottom for all of them.
I don't think we do. Although, it has seemed to me at times that we might want to have "output" be controlled by its own EXPLAIN option. EXPLAIN (VERBOSE on, OUTPUT off) ... -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
