Thread: pgsql: Add tests for UNBOUNDED syntax ambiguity

Add tests for UNBOUNDED syntax ambiguity

There is a syntactic ambiguity in the SQL standard.  Since UNBOUNDED
is a non-reserved word, it could be the name of a function parameter
and be used as an expression.  There is a grammar hack to resolve such
cases as the keyword.  Add some tests to record this behavior.

Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://www.postgresql.org/message-id/flat/b2a09a77-3c8f-7c68-c9b7-824054f87d98%40enterprisedb.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/71ba45a3602da0bdbb518e16e3990cfcf21e5f73

Modified Files
--------------
src/test/regress/expected/window.out | 140 +++++++++++++++++++++++++++++++++++
src/test/regress/sql/window.sql      |  66 +++++++++++++++++
2 files changed, 206 insertions(+)