pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rajesh Kumar Mallah <mallah.rajesh@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Lista Postgres <pgsql-admin@postgresql.org>
Subject: Re: Should duplicate indexes on same column and same table be allowed?
Date: Sun, 10 Dec 2006 00:47:04 +0530
Message-ID: <a97c77030612091117j40f9fdbejcdbb85e9aa354b8d@mail.gmail.com> (raw)
In-Reply-To: <18891.1165686391@sss.pgh.pa.us>
References: <a97c77030612082203j5b1dac19i96ef9932d60f375e@mail.gmail.com>
	<8397.1165647371@sss.pgh.pa.us>
	<a97c77030612082307l10eee309n6bd8ad15e992b3c2@mail.gmail.com>
	<a97c77030612082320v733b0bbav5ed2828edbc95a8d@mail.gmail.com>
	<18891.1165686391@sss.pgh.pa.us>

On 12/9/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Rajesh Kumar Mallah" <mallah.rajesh@gmail.com> writes:
> > Suppose an index get corrupted. And you need create a new index
> > with exact specs and then drop the old index. Is it better to
> > have a performing corrupted index or not have it at all and temporarily
> > suffer some performance degradation ?
>
> The case that was being discussed just a day or two ago was where you
> wanted to do the equivalent of REINDEX because of index bloat, not any
> functional "corruption".  In that case it's perfectly clear that
> temporarily not having the index isn't acceptable ... especially if
> it's enforcing a unique constraint.

Sorry ,
i guess i digressed .
Lemme put the question once again.

psql> CREATE INDEX x on test (col1);
psql> CREATE INDEX y on test (col1);

What is (are) the downsides of disallowing the
second index. which is *exactly* same as
previous?

Regds
mallah.

>
>                         regards, tom lane
>



view thread (13+ messages)  latest in thread

Message-ID: <a97c77030612091117j40f9fdbejcdbb85e9aa354b8d@mail.gmail.com>
Permalink:  ../a97c77030612091117j40f9fdbejcdbb85e9aa354b8d@mail.gmail.com/
Also on:    postgresql.org/message-id/a97c77030612091117j40f9fdbejcdbb85e9aa354b8d@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: mallah.rajesh@gmail.com, tgl@sss.pgh.pa.us
  Subject: Re: Should duplicate indexes on same column and same table be allowed?
  In-Reply-To: <a97c77030612091117j40f9fdbejcdbb85e9aa354b8d@mail.gmail.com>
  References: <a97c77030612082203j5b1dac19i96ef9932d60f375e@mail.gmail.com> <8397.1165647371@sss.pgh.pa.us> <a97c77030612082307l10eee309n6bd8ad15e992b3c2@mail.gmail.com> <a97c77030612082320v733b0bbav5ed2828edbc95a8d@mail.gmail.com> <18891.1165686391@sss.pgh.pa.us> <a97c77030612091117j40f9fdbejcdbb85e9aa354b8d@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox