Re: WIP: generalized index constraints - Mailing list pgsql-hackers

From Brendan Jurd
Subject Re: WIP: generalized index constraints
Date
Msg-id 37ed240d0909151021v3addf3a2hf84d9389c8c6c63c@mail.gmail.com
Whole thread Raw
In response to Re: WIP: generalized index constraints  (Robert Haas <robertmhaas@gmail.com>)
List 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.


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: hardware information
Next
From: "David E. Wheeler"
Date:
Subject: Re: Timestamp to time_t