Message-ID: <4BB40EE8.2080005@postnewspapers.com.au>
Date: Thu, 01 Apr 2010 11:11:36 +0800
From: Craig Ringer <craig@postnewspapers.com.au>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Jaime Casanova <jcasanov@systemguards.com.ec>
CC: raghavendra t <raagavendra.rao@gmail.com>,
	Kevin Grittner <Kevin.Grittner@wicourts.gov>,
	pgsql-performance@postgresql.org
Subject: Re: How to fast the REINDEX
References: <p2ubc7de5a31003311351p83987eedpbb86727ab9fa9ca3@mail.gmail.com>
	<4BB3722F02000025000302BF@gw.wicourts.gov>
	<j2tbc7de5a31003311433h5c4ce21ej79aa67067e98a4bf@mail.gmail.com>
	<j2w3073cc9b1003311525if0fccf56y3a485b26eccc82f7@mail.gmail.com>
In-Reply-To: <j2w3073cc9b1003311525if0fccf56y3a485b26eccc82f7@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Jaime Casanova wrote:
> On Wed, Mar 31, 2010 at 5:33 PM, raghavendra t
> <raagavendra.rao@gmail.com> wrote:
>>>> Why are you doing that?
>> Our table face lot of updates and deletes in a day, so we prefer reindex to
>> update the indexes as well overcome with a corrupted index.
>>
> 
> do you have a corrupted index? if not, there is nothing to do...
> REINDEX is not a mantenance task on postgres

Actually, if your free_space_map (pre 8.4) isn't up to keeping track of
bloat, or autovac isn't running enough, you're likely to get bloat of
indexes as well as tables that may need VACUUM FULL + REINDEX to
properly clean up.

It's probably better to fix your fsm/autovac settings then CLUSTER the
table so it doesn't happen again, though.

--
Craig Ringer