Redundant indexes?

From: Jeffrey Tenny <jeffrey(dot)tenny(at)comcast(dot)net>
To: pgsql-performance(at)postgresql(dot)org
Subject: Redundant indexes?
Date: 2005-05-27 21:28:01
Message-ID: 429790E1.5040308@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Would I be correct in assuming that the following two indexes are
completely redundant except for the fact that one complains about
uniqueness constraint violations and the other does not?

Or is there are legitimate use for having BOTH indexes?

I'm trying to figure out if it's okay to delete the non-unique index.
(I have a bunch of tables suffering this malady from some problematic
application code).

Table "public.erf"
Column | Type | Modifiers
--------+---------+-----------
rid | integer | not null
cid | integer | not null
Indexes: erf_rid_key unique btree (rid),
erf_rid_idx btree (rid)

Index "public.erf_rid_idx"
Column | Type
--------+---------
rid | integer
btree, for table "public.erf"

Index "public.erf_rid_key"
Column | Type
--------+---------
rid | integer
unique, btree, for table "public.erf"

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Bruce Momjian 2005-05-27 22:07:38 Re: [PERFORM] "Hash index" vs. "b-tree index" (PostgreSQL
Previous Message Eric Lauzon 2005-05-27 17:05:57 OID vs overall system performances on high load databases.