On Wed, 2005-01-26 at 15:48 -0500, Greg Stark wrote: > Well presumably you would need a non-unique index created for query execution > purposes. The unique index would be purely for enforcing the constraint.
Yuck. You could perhaps relax the uniqueness of the index during the transaction itself, and keep around some backend-local indication of which index entries it have been inserted. Then at transaction-commit you'd need to re-check the inserted index entries to verify that they are unique. It would be nice to just keep a pin on the leaf page that we inserted into, although we'd need to take care to follow subsequent page splits (could we use the existing L & Y techniques to do this?). Needless to say, it would be pretty ugly... -Neil ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
