Re: WIP: generalized index constraints

Brendan Jurd <direvus@gmail.com>

From: Brendan Jurd <direvus@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jeff Davis <pgsql@j-davis.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, pgsql-hackers@postgresql.org
Date: 2009-09-15T17:21:54Z
Lists: pgsql-hackers
2009/9/16 Robert Haas <robertmhaas@gmail.com>:
> On Tue, Sep 15, 2009 at 1:14 PM, Brendan Jurd <direvus@gmail.com> wrote:
>> 2009/9/16 Robert Haas <robertmhaas@gmail.com>:
>>> On Tue, Sep 15, 2009 at 12:54 PM, Jeff Davis <pgsql@j-davis.com> wrote:
>>>> I don't want to call them "don't overlap constraints", because it's not
>>>> limited to a non-overlapping constraint.
>>>
>>> Oh.  What else can you do with it?
>>
>> Anything that there is an operator for.
>
> Uhh.... so what happens if I create an index constraint using the
> +(integer, integer) operator?

Okay, so my first answer was a simplification.  You can use any
operator that has an appropriate index strategy entry.