Make the OVER keyword unreserved.
This results in a slightly less specific error message when OVER
is used in a context where we don't accept window functions, but
per discussion, it's worth it to get the benefit of not needing
to reserve this keyword any more. This same refactoring will
also let us avoid reserving some other keywords that we expect
to add in upcoming patches (specifically, IGNORE, RESPECT, and
FILTER).
Troels Nielsen, with minor changes by me
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/5893ffa79c03824f34ae3d37f211381fd1c17283
Modified Files
--------------
src/backend/parser/gram.y | 90 ++++++++++++++++++++++------------
src/include/parser/kwlist.h | 2 +-
src/test/regress/expected/window.out | 4 +-
3 files changed, 63 insertions(+), 33 deletions(-)
