"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> sample: select mleast(variadic array[1,2,3,4,5]);
One other point here: in the patch as presently submitted, VARIADIC
can't be an unreserved keyword, but it seems to be enough to make it a
col_name_keyword. Some preliminary testing says that that doesn't work
anymore after adding productions to allow the above: VARIADIC will have
to become a fully reserved keyword. That's a bit annoying, since it's
not reserved according to the SQL spec, but it doesn't seem like a word
that's really likely to be in use as a user identifier. Does anyone
think this issue is a showstopper?
regards, tom lane
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
