> On Wed, Jun 8, 2016 at 7:13 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> It appears that the new <-> operator has been made to have exactly the
>> same grammatical precedence as the existing & (AND) operator. Thus,
>> for example, 'a & b <-> c'::tsquery means something different from
>> 'b <-> c & a'::tsquery:
>> I find this surprising. My intuitive feeling is that <-> ought to
>> bind tighter than & (and therefore also tighter than |). What's
>> the reasoning for making it act like this?
>
> ah, now we remember :) The idea about equivalence of & and <->
> operators appeared in situation when <-> degenerates to & in case of
> absence of positional information. Looks like we mixed different
> things, will fix.
Attached patch changes a precedences of operations to |, &, <->, | in ascending
order. BTW, it simplifies a bit a code around printing and parsing of tsquery.
--
Teodor Sigaev E-mail: teodor@sigaev.ru
WWW: http://www.sigaev.ru/
