Re: EXPLAIN doesn't show the actual function expression for FunctionScan

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: EXPLAIN doesn't show the actual function expression for FunctionScan
Date: 2010-08-24 17:13:27
Message-ID: AANLkTi=8RKW0s5P8dJ0kZwBeL1otuJ9ST5W7_HjDEC32@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 24, 2010 at 5:06 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pei He 2010-08-24 17:13:29 About debug two versions of postgresql in eclipse
Previous Message David Fetter 2010-08-24 17:03:45 Re: EXPLAIN doesn't show the actual function expression for FunctionScan