Re: WIP: generalized index constraints
Jeff Davis <pgsql@j-davis.com>
From: Jeff Davis <pgsql@j-davis.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Brendan Jurd <direvus@gmail.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, pgsql-hackers@postgresql.org
Date: 2009-09-15T17:28:28Z
Lists: 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