Re: extended operator classes vs. type interfaces
От | Robert Haas |
---|---|
Тема | Re: extended operator classes vs. type interfaces |
Дата | |
Msg-id | k2q603c8f071004100923o40a8a2dcna625af7ff6cf0448@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: extended operator classes vs. type interfaces (Yeb Havinga <yebhavinga@gmail.com>) |
Ответы |
Re: extended operator classes vs. type interfaces
|
Список | 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 по дате отправления: