Re: operator dependency of commutator and negator, redux - Mailing list pgsql-hackers

From Brendan Jurd
Subject Re: operator dependency of commutator and negator, redux
Date
Msg-id CADxJZo0HHSadQcK-aeqrG0Rnph46hRTDN_HTACp55a+fdJ_HnQ@mail.gmail.com
Whole thread Raw
In response to operator dependency of commutator and negator, redux  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: operator dependency of commutator and negator, redux  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 20 December 2012 11:51, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> While reconsidering the various not-too-satisfactory fixes we thought of
> back then, I had a sudden thought.  Instead of having a COMMUTATOR or
> NEGATOR forward reference create a "shell" operator and link to it,
> why not simply *ignore* such references?  Then when the second operator
> is defined, go ahead and fill in both links?


Ignore with warning sounds pretty good.  So it would go something like this?

# CREATE OPERATOR < (... COMMUTATOR >);
WARNING: COMMUTATOR > (foo, foo) undefined, ignoring.
CREATE OPERATOR

# CREATE OPERATOR > (... COMMUTATOR <);
CREATE OPERATOR


Cheers,
BJ



pgsql-hackers by date:

Previous
From: Ronan Dunklau
Date:
Subject: Re: FDW: ForeignPlan and parameterized paths
Next
From: Gavin Flower
Date:
Subject: Re: discarding duplicate indexes