On Tue, Jul 10, 2012 at 11:11 AM, Greg Stark <st...@mit.edu> wrote: > On Tue, Jul 10, 2012 at 3:44 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > >> The problem you describe is one of constraints and dependencies and > >> not one of indexes. It seems what you really want is a way to alter > >> foreign key dependencies to depend on a new index. Either an explicit > >> command that lets you set the new dependency or what seems even better > >> would be to have DROP INDEX check any dependent objects to see if > >> there's another index that can satisfy them and change their > >> dependency. > > > > Either of these have exactly the same issue, namely their correctness > > depends on determining if two indexes have identical properties. > > This doesn't sound right to me. In these cases all it would have to > know about is the same set of properties that CREATE CONSTRAINT looks > for to find a satisfactory index to depend on. >
I like the DROP index idea, but the silent side-effect may not make people happy. Can you give me a pointer to relevant code. -- Gurjeet Singh EnterpriseDB Corporation The Enterprise PostgreSQL Company
