aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2013-06-02 20:09:32 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2013-06-02 20:09:32 -0400
commit1e5588cfd966ef5f4a1e31625b7079cff6d91a5a (patch)
tree5e689668996daba0c418e9009d8d5d0903aed9ae /src/tutorial
parent39485bbdbadab26287e097474bb63acda4593abb (diff)
downloadpostgresql-1e5588cfd966ef5f4a1e31625b7079cff6d91a5a.tar.gz
postgresql-1e5588cfd966ef5f4a1e31625b7079cff6d91a5a.zip
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.
Diffstat (limited to 'src/tutorial')
0 files changed, 0 insertions, 0 deletions