Re: extended operator classes vs. type interfaces - Mailing list pgsql-hackers

From Robert Haas
Subject Re: extended operator classes vs. type interfaces
Date
Msg-id k2q603c8f071004100923o40a8a2dcna625af7ff6cf0448@mail.gmail.com
Whole thread Raw
In response to Re: extended operator classes vs. type interfaces  (Yeb Havinga <yebhavinga@gmail.com>)
Responses Re: extended operator classes vs. type interfaces  (Yeb Havinga <yebhavinga@gmail.com>)
List pgsql-hackers
On Sat, Apr 10, 2010 at 12:05 PM, Yeb Havinga <yebhavinga@gmail.com> wrote:
> Jeff Davis wrote:
>>
>> To give some context, I started a thread a while ago:
>>
>> http://archives.postgresql.org/pgsql-hackers/2009-10/msg01403.php
>>
>
> Interesting, a join type for overlaps, which makes me think a bit of the
> staircase join for pre-post coordinates. However, does a join operator type
> need certain kinds of properties of the operator involved, e.g. being
> commutative, transitive etc? Else the join reordering fails. The latter
> fails for the overlap operator.

I don't think I follow this.  As far as I know, the join order
constraints don't depend on the choice of operator.

...Robert


pgsql-hackers by date:

Previous
From: Yeb Havinga
Date:
Subject: Re: extended operator classes vs. type interfaces
Next
From: "Kevin Grittner"
Date:
Subject: Re: GSoC - proposal - Materialized Views in PostgreSQL