Re: operator dependency of commutator and negator, redux

From: Brendan Jurd <direvus(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: operator dependency of commutator and negator, redux
Date: 2012-12-20 06:40:51
Message-ID: CADxJZo0HHSadQcK-aeqrG0Rnph46hRTDN_HTACp55a+fdJ_HnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 20 December 2012 11:51, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Flower 2012-12-20 08:26:44 Re: discarding duplicate indexes
Previous Message Ronan Dunklau 2012-12-20 05:38:44 Re: FDW: ForeignPlan and parameterized paths