2009/7/17 Jeff Davis <pg...@j-davis.com>: > Another idea that I thought about is that: > > ALTER TABLE foo ADD UNIQUE (a, b) USING foo_idx; > > could be a shorthand for: > > ALTER TABLE foo ADD INDEX CONSTRAINT (a =, b =) USING foo_idx; > > The benefit is that it could go over GiST indexes or hash indexes, not > just btrees. The syntax could also be useful to turn an existing btree > into a unique btree.
I like that idea ... although how would this interact (if at all) with the existing pg_index.isunique flag? Would it become deprecated in favour of using indconstrats, or would you actually look at switching isunique to TRUE if somebody applies a constraint which is made up entirely of equality ops? Cheers, BJ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
