Skip to content
Snippets Groups Projects
  • Tom Lane's avatar
    17a22a74
    Allow type_func_name_keywords in some places where they weren't before. · 17a22a74
    Tom Lane authored
    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.
    17a22a74
    History
    Allow type_func_name_keywords in some places where they weren't before.
    Tom Lane authored
    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.