From: | Steve Clark <sclark(at)netwolves(dot)com> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, raghavendra t <raagavendra(dot)rao(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: How to fast the REINDEX |
Date: | 2010-04-01 11:10:13 |
Message-ID: | 4BB47F15.4000307@netwolves.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 03/31/2010 11:11 PM, Craig Ringer wrote:
> Jaime Casanova wrote:
>> On Wed, Mar 31, 2010 at 5:33 PM, raghavendra t
>> <raagavendra(dot)rao(at)gmail(dot)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
>
So am I to understand I don't need to do daily reindexing as a maintenance
measure with 8.3.7 on FreeBSD.
--
Stephen Clark
NetWolves
Sr. Software Engineer III
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve(dot)clark(at)netwolves(dot)com
www.netwolves.com
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2010-04-01 11:36:54 | Re: How to fast the REINDEX |
Previous Message | Hannu Krosing | 2010-04-01 10:54:33 | Re: How to fast the REINDEX |