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

From Robert Haas
Subject Re: WIP: generalized index constraints
Date
Msg-id 603c8f070909151016u533eed80j927a0600f5624a3f@mail.gmail.com
Whole thread Raw
In response to Re: WIP: generalized index constraints  (Brendan Jurd <direvus@gmail.com>)
Responses Re: WIP: generalized index constraints
Re: WIP: generalized index constraints
List pgsql-hackers
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?

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: errcontext support in PL/Perl
Next
From: Tom Lane
Date:
Subject: Re: Timestamp to time_t