On Fri, Nov 6, 2009 at 1:02 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>>> BTW, this brings up another point, which is that up to now it's often
>>> been possible to use plpgsql variable names that conflict with
>>> core-parser reserved words, so long as you didn't need to use the
>>> reserved word with its special meaning. That will stop working when
>>> this patch goes in. Doesn't bother me any, but if anyone thinks it's
>>> a serious problem, speak now.
>
>> Any keyword or just fully reserved keywords?
>
> Anything that's not allowed as a column name will be at issue.
Well, that's not so bad. If it included unreserved keywords I think
that would be more of an issue.
...Robert
