Re: Odd/undocumented precedence of concatenation operator - Mailing list pgsql-hackers

From Shay Rojansky
Subject Re: Odd/undocumented precedence of concatenation operator
Date
Msg-id CADT4RqCan+5ngig_uZ12SYONNmA-tcRVid8ck5WnOMcUF6wApw@mail.gmail.com
Whole thread Raw
In response to Re: Odd/undocumented precedence of concatenation operator  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
It is expected, and documented.  (It's also different in 9.5, see
http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=c6b3c939b7e0f1d35f4ed4996e71420a993810d2)

Ah, thanks!
 
> If nothing else, it seems that the concatenation operator should be listed
> on the operator precedence table at
> http://www.postgresql.org/docs/9.4/static/sql-syntax-lexical.html#SQL-PRECEDENCE-TABLE

Both >= and || fall into the "any other operator" case, no?
 
I somehow missed that in the table, assuming that >= would be somewhere with > and =. Thanks again.

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: function parse_ident
Next
From: "Shulgin, Oleksandr"
Date:
Subject: Re: On-demand running query plans using auto_explain and signals