pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: raghavendra t <raagavendra.rao@gmail.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to fast the REINDEX
Date: Thu, 1 Apr 2010 03:17:22 +0530
Message-ID: <y2rbc7de5a31003311447z44c0841ey9f5d9d6d41d2ca06@mail.gmail.com> (raw)
In-Reply-To: <4BB37AE402000025000302C5@gw.wicourts.gov>
References: <p2ubc7de5a31003311351p83987eedpbb86727ab9fa9ca3@mail.gmail.com>
	<4BB3722F02000025000302BF@gw.wicourts.gov>
	<j2tbc7de5a31003311433h5c4ce21ej79aa67067e98a4bf@mail.gmail.com>
	<4BB37AE402000025000302C5@gw.wicourts.gov>

>
> 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
>

view thread (19+ messages)  latest in thread

Message-ID: <y2rbc7de5a31003311447z44c0841ey9f5d9d6d41d2ca06@mail.gmail.com>
Permalink:  ../y2rbc7de5a31003311447z44c0841ey9f5d9d6d41d2ca06@mail.gmail.com/
Also on:    postgresql.org/message-id/y2rbc7de5a31003311447z44c0841ey9f5d9d6d41d2ca06@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-performance@postgresql.org
  Cc: raagavendra.rao@gmail.com, Kevin.Grittner@wicourts.gov
  Subject: Re: How to fast the REINDEX
  In-Reply-To: <y2rbc7de5a31003311447z44c0841ey9f5d9d6d41d2ca06@mail.gmail.com>
  References: <p2ubc7de5a31003311351p83987eedpbb86727ab9fa9ca3@mail.gmail.com> <4BB3722F02000025000302BF@gw.wicourts.gov> <j2tbc7de5a31003311433h5c4ce21ej79aa67067e98a4bf@mail.gmail.com> <4BB37AE402000025000302C5@gw.wicourts.gov> <y2rbc7de5a31003311447z44c0841ey9f5d9d6d41d2ca06@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