Skip site navigation (1) Skip section navigation (2)

Re: How to fast the REINDEX

From: raghavendra t <raagavendra(dot)rao(at)gmail(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: How to fast the REINDEX
Date: 2010-03-31 21:47:22
Message-ID: y2rbc7de5a31003311447z44c0841ey9f5d9d6d41d2ca06@mail.gmail.com (view raw or flat)
Thread:
Lists: 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(dot)Grittner(at)wicourts(dot)gov>wrote:

> raghavendra t <raagavendra(dot)rao(at)gmail(dot)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
>

In response to

Responses

pgsql-performance by date

Next:From: Kevin GrittnerDate: 2010-03-31 21:51:55
Subject: Re: How to fast the REINDEX
Previous:From: Kevin GrittnerDate: 2010-03-31 21:40:04
Subject: Re: How to fast the REINDEX

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group