Re: EXPLAIN doesn't show the actual function expression for FunctionScan - Mailing list pgsql-hackers

From Greg Stark
Subject Re: EXPLAIN doesn't show the actual function expression for FunctionScan
Date
Msg-id AANLkTi=8RKW0s5P8dJ0kZwBeL1otuJ9ST5W7_HjDEC32@mail.gmail.com
Whole thread Raw
In response to Re: EXPLAIN doesn't show the actual function expression for FunctionScan  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: EXPLAIN doesn't show the actual function expression for FunctionScan  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Aug 24, 2010 at 5:06 PM, Tom Lane <tgl@sss.pgh.pa.us> 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.

On the other hand the plan tree does read from bottom up with the
outputs going up to the next level up.


--
greg


pgsql-hackers by date:

Previous
From: Pei He
Date:
Subject: About debug two versions of postgresql in eclipse
Next
From: Tom Lane
Date:
Subject: Re: [ADMIN] Unable to drop role