Re: operator precedence issues - Mailing list pgsql-hackers

From Tom Lane
Subject Re: operator precedence issues
Date
Msg-id 15949.1378217592@sss.pgh.pa.us
Whole thread Raw
In response to Re: operator precedence issues  (Andres Freund <andres@2ndquadrant.com>)
Responses operator precedence issues
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2013-09-03 08:59:53 -0500, Merlin Moncure wrote:
>> While playing around with Andres's trick, I noticed that it works but
>> will not match against operators taking "any" although those will
>> match with explicit schema declaration (FWICT it goes through the
>> search_path trying to explicitly match int/int operator then goes
>> again matches "any").  That's pretty weird:

> Not surprising. We look for the best match for an operator and
> explicitly matching types will be that. If there were no operator(int,
> int) your anyelement variant should get called.

Yeah, this has exactly nothing to do with operator precedence.
Precedence is about which operator binds tighter in cases like "A+B*C".
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: operator precedence issues
Next
From: Blake Smith
Date:
Subject: Re: Hstore: Query speedups with Gin index