| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Add tests for UNBOUNDED syntax ambiguity |
| Date: | 2021-07-01 07:34:20 |
| Message-ID: | E1lyrDI-000762-Vg@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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(at)iki(dot)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(+)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2021-07-01 08:58:27 | pgsql: Fix build failure with newer ICU |
| Previous Message | David Rowley | 2021-07-01 03:29:38 | pgsql: Improve various places that double the size of a buffer |