| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "William Garrison" <postgres(at)mobydisk(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: automatic REINDEX-ing |
| Date: | 2008-08-12 16:19:13 |
| Message-ID: | dcc563d10808120919gdc7f002q598c3df11d867b72@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Aug 12, 2008 at 10:09 AM, William Garrison
<postgres(at)mobydisk(dot)com> wrote:
> Tom Lane wrote:
>>
>> Joao Ferreira gmail <joao(dot)miguel(dot)c(dot)ferreira(at)gmail(dot)com> writes:
>>
>>>
>>> I executed REINDEX by hand and the disk ocupation imediatelly dropped 6
>>> Giga...!!!
>>>
>>
>>
>>>
>>> is there a way to configure postgres to automatically execute the needed
>>> REINDEXING (on indexes and tables) for a given database....
>>>
>>
>> Generally speaking, there shouldn't be a need for "automatic
>> reindexing". What the above suggests is that you need more aggressive
>> routine vacuuming, so that you don't get into this situation in the
>> first place.
>>
>> BTW, "more aggressive routine vacuuming" does NOT mean "use vacuum full".
>> Vacuum full tends to make index bloat worse, not better.
>>
>
> So now that we know what that term does not mean, what does it mean? Just
> doing it more often by adjusting the autovacuum parameters?
exactly. Or running cronned vacuums on particular tables if they need
it more often.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Porkodi Yesu | 2008-08-12 16:20:46 | psql tutorial |
| Previous Message | William Garrison | 2008-08-12 16:09:50 | Re: automatic REINDEX-ing |