Re: Does "verbose" Need to be Reserved? - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: Does "verbose" Need to be Reserved?
Date
Msg-id 87vdg6oerq.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Does "verbose" Need to be Reserved?  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: Does "verbose" Need to be Reserved?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>>>>> "David" == "David E Wheeler" <david@kineticode.com> writes:
David> Hey All,David> I was just getting a new version of pgTAP ready for release, and while testing it on HEAD, I got
thiserror: 
David> + psql:pgtap.sql:5789: ERROR:  syntax error at end of inputDavid> + LINE 28:                 IF verbose THEN
RETURNNEXT diag(tests[i] ||...David> +                                    ^ 
David> I asked on IRC, and Andrew “RhodiumToad” Gierth pointed outDavid> that it became a reserved word at some point.
I'mfine toDavid> rename my variable, but Andew and I were wondering if it'sDavid> really necessary for "verbose" to be
reserved,since it's notDavid> in the spec. 

Looking at it more closely, this is likely to be fallout from the
plpgsql lexer/parser changes; it probably worked before only because
plpgsql was doing its own thing rather than using the main lexer.

VERBOSE has been reserved all along in order to distinguish
'vacuum verbose;' from 'vacuum tablename;' and so on; but it's still an
interesting pitfall for plpgsql users.

--
Andrew (irc:RhodiumToad)


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Range types
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Range types