Re: How to fast the REINDEX - Mailing list pgsql-performance

From raghavendra t
Subject Re: How to fast the REINDEX
Date
Msg-id y2rbc7de5a31003311447z44c0841ey9f5d9d6d41d2ca06@mail.gmail.com
Whole thread Raw
In response to Re: How to fast the REINDEX  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: How to fast the REINDEX
List pgsql-performance
If this is a one-time fix for a corrupted index, did you look at
CREATE INDEX CONCURRENTLY?  You could avoid any down time while you
fix things up.
Using CREATE INDEX CONCURRENTLY will avoid the exclusive locks on the table, but my question is, how to get a performance on the existing indexes. You mean to say , drop the existing indexes and create the index with CONCURRENTLY. Does this give the performance back.
 
Regards
Raghavendra
 
 
On Thu, Apr 1, 2010 at 3:10 AM, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote:
raghavendra t <raagavendra.rao@gmail.com> wrote:

> overcome with a corrupted index.

If this is a one-time fix for a corrupted index, did you look at
CREATE INDEX CONCURRENTLY?  You could avoid any down time while you
fix things up.

http://www.postgresql.org/docs/8.4/interactive/sql-createindex.html

-Kevin

pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: How to fast the REINDEX
Next
From: "Kevin Grittner"
Date:
Subject: Re: How to fast the REINDEX