On Tue, Aug 24, 2010 at 12:06:34PM -0400, Tom Lane wrote: > I wrote: > > Robert Haas <robertmh...@gmail.com> writes: > >> 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, ...) > > > Yeah, that's what I had in mind, but I'm still fumbling for the right > > label. "Expression" seems a bit too generic. > > How about "Function Call"? > > A moment's hacking later: > > regression=# explain verbose SELECT lv|| op|| rv FROM unnest(ARRAY[ > ROW('1.2.2'::semver, '='::text, '1.2.2'::semver), > ROW('1.2.23', '=', '1.2.23') > ]) AS f(lv semver, op text, rv semver); > QUERY PLAN > > -------------------------------------------------------------------------------------------------------------------------------- > 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')]) > (3 rows) > > Look reasonable?
This would have helped me a good deal a couple of times this week :) Cheers, David. -- David Fetter <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers