| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, "Jeff Davis" <pgsql(at)j-davis(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: variadic function support |
| Date: | 2008-07-14 20:22:48 |
| Message-ID: | 2135.1216066968@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
"Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2008-07-14 22:15:01 | Re: variadic function support |
| Previous Message | Gregory Stark | 2008-07-14 18:24:14 | Re: [PATCHES] VACUUM Improvements - WIP Patch |