Re: operator precedence issues - Mailing list pgsql-hackers

From Andres Freund
Subject Re: operator precedence issues
Date
Msg-id 20130830224852.GA11360@awork2.anarazel.de
Whole thread Raw
In response to operator precedence issues  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: operator precedence issues  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
Hi,

On 2013-08-30 17:35:04 -0500, Merlin Moncure wrote:
> "When a schema-qualified operator name is used in the OPERATOR syntax,
> as for example in:
> SELECT 3 OPERATOR(pg_catalog.+) 4;
> the OPERATOR construct is taken to have the default precedence shown
> in Table 4-2 for "any other" operator. This is true no matter which
> specific operator appears inside OPERATOR()."
> 
> That rule seems intentionally designed to make it impossible to to
> override mathematical behaviors.  Mainly curious -- was that
> intentional?

You can change your search_path to include your schema before an
explicitly listed pg_catalog afair. Not nice, but should work...

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: operator precedence issues
Next
From: Tom Lane
Date:
Subject: Re: Variadic aggregates vs. project policy