pgsql: Allow type_func_name_keywords in some places where they weren't - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Allow type_func_name_keywords in some places where they weren't
Date
Msg-id E1UjILc-0002Ms-Be@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Allow type_func_name_keywords in some places where they weren't before.

This change makes type_func_name_keywords less reserved than they were
before, by allowing them for role names, language names, EXPLAIN and COPY
options, and SET values for GUCs; which are all places where few if any
actual keywords could appear instead, so no new ambiguities are introduced.

The main driver for this change is to allow "COPY ... (FORMAT BINARY)"
to work without quoting the word "binary".  That is an inconsistency that
has been complained of repeatedly over the years (at least by Pavel Golub,
Kurt Lidl, and Simon Riggs); but we hadn't thought of any non-ugly solution
until now.

Back-patch to 9.0 where the COPY (FORMAT BINARY) syntax was introduced.

Branch
------
REL9_2_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/17a22a74a73a0fc11ef7a590aecebd98982a7169

Modified Files
--------------
src/backend/parser/gram.y |   53 +++++++++++++++++++++++++--------------------
1 file changed, 30 insertions(+), 23 deletions(-)


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Another man page whitespace fix
Next
From: Tom Lane
Date:
Subject: pgsql: Allow type_func_name_keywords in some places where they weren't