Re: fix - function call with variadic parameter for type "any" - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: fix - function call with variadic parameter for type "any"
Date
Msg-id 162867790904021323l6f13dca1u48cc9bb93d20d2c3@mail.gmail.com
Whole thread Raw
In response to Re: fix - function call with variadic parameter for type "any"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: fix - function call with variadic parameter for type "any"
List pgsql-hackers
2009/4/2 Tom Lane <tgl@sss.pgh.pa.us>:
> Pavel Stehule <pavel.stehule@gmail.com> writes:
>> Our implementation of variadic parameters are not complete. The
>> support of "any" type is incomplete. Modificator VARIADIC for funccall
>> parameters needs transformation from ArrayExpr to standard parameters
>> list.
>
> I don't think I agree with this change.  The point of an ANY function
> is that the function is going to do its own coping with the presented
> arguments.  This patch takes away the flexibility to do that and instead
> enforces one very restrictive view of what the intended behavior is.

ok, but then an function have to be noticed about using VARIADIC
parameter's modificator.

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.

regards
Pavel Stehule

>
>                        regards, tom lane
>


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [pgsql-www] Mentors needed urgently for SoC & PostgreSQL Student Internships
Next
From: Simon Riggs
Date:
Subject: Re: [COMMITTERS] pgsql: If we expect a hash join to be performed in multiple batches,