From: | S Arvind <arvindwill(at)gmail(dot)com> |
---|---|
To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Vacuuming technique doubt |
Date: | 2009-06-01 18:01:37 |
Message-ID: | abf9211d0906011101h356d0670xfe7c3fdadbf73dc6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi Smith,
The reason why we need it manually is , we don't need any performance drop
in our production hours. So we figured out the most less usage working time,
most freq used tables and want to perform that on daily . so in weekends we
can vaccum and reindex entire db.. Is the model is not more efficient Smith?
-Arvind S
*
"Many of lifes failure are people who did not realize how close they were to
success when they gave up."
-Thomas Edison
*
On Mon, Jun 1, 2009 at 9:04 PM, Greg Smith <gsmith(at)gregsmith(dot)com> wrote:
> On Mon, 1 Jun 2009, S Arvind wrote:
>
> Having a doubt, we want to vacuum and reindex some 50 most used tables
>> daily on specific time. Is it best to have a function in
>> postgres and call it in cron or is there any other good way to do the two
>> process for specified tables at specified time?
>>
>
> If you haven't been using VACUUM properly, it's possible to get into a
> position where you need to REINDEX your tables and go through the sort of
> giant cleanup step you describe. If you think you need to do that daily,
> though, you probably should take a look at tuning autovacuum rather than
> trying to fix the problem manually all the time.
>
> --
> * Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
>
From | Date | Subject | |
---|---|---|---|
Next Message | Anne Rosset | 2009-06-01 18:14:47 | Re: Unexpected query plan results |
Previous Message | Matthew Wakeling | 2009-06-01 16:37:32 | Re: Very inefficient query plan with disjunction in WHERE clause |