On Tue, Aug 24, 2010 at 11:06 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Tue, Aug 24, 2010 at 10:56 AM, Robert Haas <robertmhaas@gmail.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.
If you try to put all that on the same line, I think it might get
awkwardly long. Perhaps something like:
Function Scan on function_name Expression: function_name(function_arg1, function_arg2, ...)
?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company