pgsql: Allow type_func_name_keywords in some places where they weren't

Поиск
Список
Период
Сортировка
От Tom Lane
Тема pgsql: Allow type_func_name_keywords in some places where they weren't
Дата
Msg-id E1UjILc-0002Mz-DB@gemulon.postgresql.org
обсуждение исходный текст
Список 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_0_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/805730d0604519facaffaa0d899e6884d0542fc0

Modified Files
--------------
src/backend/parser/gram.y |   43 +++++++++++++++++++++++++------------------
1 file changed, 25 insertions(+), 18 deletions(-)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Allow type_func_name_keywords in some places where they weren't
Следующее
От: Tom Lane
Дата:
Сообщение: pgsql: Allow type_func_name_keywords in some places where they weren't