Re: FK Constraint on index not PK

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Stéphane Schildknecht <stephane(dot)schildknecht(at)postgresqlfr(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: FK Constraint on index not PK
Date: 2007-01-12 17:57:25
Message-ID: 1168624645.9512.16.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

Joshua D. Drake

> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Ribe 2007-01-12 17:59:11 Re: Checkpoint request failed on version 8.2.1.
Previous Message Jim C. Nasby 2007-01-12 17:25:55 Re: [HACKERS] Checkpoint request failed on version 8.2.1.