Stéphane Schildknecht wrote: > Joshua D. Drake a écrit : > > On Fri, 2007-01-12 at 17:50 +0100, Stéphane Schildknecht wrote: > > > >> Dear community members, > >> > >> I'm having a quite strange behaviour while trying to drop some index. > >> > >> We have some tables with two indexes on a primary key. The first one was > >> automatically created by the primary constraint. The second one was > >> manually created on the same column. Don't know why, but I would now > >> want to suppress it. > >> > > > > Drop the second index. It is redundant. > > I know it. But I can't. The problem is that the constraint was defined with a dependence on the second index. I guess what you could do is drop the constraint, drop the second index, and then recreate the constraint. Try it within a transaction block, just in case it doesn't work (but I don't see why it wouldn't) -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
