From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Unique constraints for non-btree indexes |
Date: | 2006-01-18 21:18:10 |
Message-ID: | 2984.1137619090@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> I guess what you're talking about is a constrained index, of which a
> unique index is just a particular type. I suppose the actual constraint
> would be one of the operators defined for the operator class (since
> whatever the test is, it needs to be indexable). Although some would
> obviously be more useful than others...
I think the generalization that would be appropriate for GIST is that
a "unique" index guarantees there are no two entries x, y such that
x ~ y, where ~ is some boolean operator nominated by the opclass. We'd
probably have to insist that ~ is commutative (x ~ y iff y ~ x).
Concurrent insertion into a unique GIST index seems a bit nasty. In
btree we can identify a unique page to lock for any given key value
to ensure that no one else is concurrently inserting a conflicting
key, thus usually allowing concurrent insertions of different keys.
But I don't see how you do that for an arbitrary ~ operator.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-01-18 21:28:43 | Re: [HACKERS] Docs off on ILIKE indexing? |
Previous Message | Tom Lane | 2006-01-18 21:10:16 | Re: Unique constraints for non-btree indexes |