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

From Jeff Davis
Subject Re: WIP: generalized index constraints
Date
Msg-id 1253035708.24770.88.camel@jdavis
Whole thread Raw
In response to Re: WIP: generalized index constraints  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: WIP: generalized index constraints
Re: WIP: generalized index constraints
Re: WIP: generalized index constraints
List pgsql-hackers
On Tue, 2009-09-15 at 13:16 -0400, Robert Haas wrote:
> Uhh.... so what happens if I create an index constraint using the
> +(integer, integer) operator?

You can use any operator that has an index search strategy. Overlaps is
probably the most useful, but you could imagine other operators, like a
bi-directional containment operator (either LHS is contained in RHS, or
vice-versa).

You can also get creative and have a "similarity" operator that
determines whether two tuples are "too similar". As long as it is
symmetric, the feature will work.

Or just use wrap random() in an operator and see what happens ;)

Regards,Jeff Davis



pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Timestamp to time_t
Next
From: Robert Haas
Date:
Subject: Re: WIP: generalized index constraints