Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: EXPLAIN doesn't show the actual function expression for FunctionScan
Date: 2010-08-25 14:18:38
Message-ID: 19397.1282745918@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Dimitri Fontaine <dfontaine(at)hi-media(dot)com> writes:
> Argument List?

Well, as shown in the example I posted, it's not just the argument list
but the whole call:

>> Function Call: unnest(ARRAY[ROW(('1.2.2'::text)::semver, '='::text, ('1.2.2'::text)::semver), ROW('1.2.23', '=', '1.2.23')])

Now you might suggest that the function itself is redundant with the
information given in the FunctionScan node line and so we need only
show the argument list.  Unfortunately there are cases where this fails;
in particular, the named function could have been "inlined" by the
planner, meaning that the actual expression could be just about anything
at all.  So I think that trying to be cute is a bad idea and we should
just print the nodetree as-is.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-08-25 14:18:43
Subject: Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP)
Previous:From: Markus WannerDate: 2010-08-25 14:17:42
Subject: Re: Version Numbering

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group