| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Stéphane Schildknecht <stephane(dot)schildknecht(at)postgresqlfr(dot)org> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: FK Constraint on index not PK |
| Date: | 2007-01-13 13:43:57 |
| Message-ID: | 20070113134357.GS27743@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Kmetec | 2007-01-13 14:47:18 | index type for indexing long texts |
| Previous Message | Richard Huxton | 2007-01-13 13:10:45 | Re: FK Constraint on index not PK |