From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | S Arvind <arvindwill(at)gmail(dot)com>, "<Greg Smith" <gsmith(at)gregsmith(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Vacuuming technique doubt |
Date: | 2009-06-02 00:41:04 |
Message-ID: | 603c8f070906011741o57b56638xda87ab7ed7c29908@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, Jun 1, 2009 at 8:35 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> S Arvind <arvindwill(at)gmail(dot)com> wrote:
>
>> 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..
>
> By the time you get to your mass reindex the bloat will be harming
> your performance much more than the autovacuum needs to do. Check the
> documentation here:
>
> http://www.postgresql.org/docs/8.3/interactive/runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-VACUUM-COST
>
> I hope this helps.
But before you try that, try just using the default settings and see
if you actually have a problem.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Mayer | 2009-06-02 00:42:19 | Re: Scalability in postgres |
Previous Message | Kevin Grittner | 2009-06-02 00:35:24 | Re: Vacuuming technique doubt |