From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: EXPLAIN doesn't show the actual function expression for FunctionScan |
Date: | 2010-08-24 15:06:02 |
Message-ID: | 29138.1282662362@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Aug 24, 2010 at 10:56 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> I think showing it always is reasonable. I'd like to see it printed
>> in a form such that casting to regproc will succeed.
> On second thought, that second sentence may not make sense.
It does not, because it's not the *name* of the function that I care
about --- it's the actual executable expression including arguments.
> What exactly did you have in mind for this to look like?
Wheeler's example involves
select ... from unnest(array[blah blah blah])
and I'd like it to regurgitate the whole unnest(array[blah blah blah])
expression. Not sure how to label it exactly. Right now you only see
Function Scan on unnest f (cost=0.00..1.50 rows=100 width=96)
or with VERBOSE, it'll give you some info about the targetlist (the ...
above), but still nothing about the FROM expression.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2010-08-24 15:06:27 | Re: Typing Records |
Previous Message | Robert Haas | 2010-08-24 14:59:40 | Re: EXPLAIN doesn't show the actual function expression for FunctionScan |