Re: Remove useless associativity/precedence from parsers - Mailing list pgsql-hackers

On 2019-May-28, Andrew Gierth wrote:

> The main cases I know of are:
> 
> 1. RANGE UNBOUNDED PRECEDING - this one is actually a defect in the
> standard SQL grammar, since UNBOUNDED is a non-reserved keyword and so
> it can also appear as a legal <identifier>, and the construct
> RANGE <unsigned value specification> PRECEDING allows <identifier> to
> appear as a <SQL parameter reference>.

Should we report this to the SQL committee?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services