From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: fix - function call with variadic parameter for type "any" |
Date: | 2009-04-02 20:39:25 |
Message-ID: | 26576.1238704765@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> actually, there isn't any difference between a) and b)
> a) select somevariadicwithany(10);
> b) select somevariadicwithany(variadic 10);
> in this case the keyword VARIADIC is ignored.
Well, in my mind what the VARIADIC keyword does is it prevents the parser
from building an ARRAY[] expression around the remaining parameters.
Which would be incorrect for a VARIADIC ANY function because such a
function presumably doesn't want to force all the actual arguments
to be the same type --- if it did, it could use VARIADIC ANYARRAY.
VARIADIC ANY basically exists to allow an ANY-argument function to
accept any number of ANY parameters. As such, PG_NARGS() is all it
really needs to know, plus the already-existing support for obtaining
the parameters' actual datatypes.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2009-04-02 21:00:51 | Re: Additional DTrace Probes |
Previous Message | Simon Riggs | 2009-04-02 20:32:56 | Re: [COMMITTERS] pgsql: If we expect a hash join to be performed in multiple batches, |