From: | Vinubalaji Gopal <vgopal(at)abaca(dot)com> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | "Pgsql-Performance ((E-mail))" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: best way to run maintenance script |
Date: | 2008-03-15 05:07:45 |
Message-ID: | 1205557665.12661.51.camel@vinu-ubuntu.abaca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
>
> I think you will find if you do it the right way, which is to say the
> way that it is meant to be done with the configurable options, your
> life will be a great deal more pleasant than some one off hack.
>
yeah I agree. The pg_maintanence script which calls vacuum and analyze
is the one of the thing that is causing more problems. I am trying out
various vacuum options (vacuum_cost_limit, vacuum_cost_delay) and
finding it hard to understand the implications of the variables. What
are the optimal values for the vacuum_* parameters - for a really active
database (writes at the rate of ~ 50 rows/seconds).
I started with
vacuum_cost_delay = 200
vacuum_cost_limit = 400
and that did not help much.
--
Vinu
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2008-03-15 12:46:04 | Re: best way to run maintenance script |
Previous Message | Vinubalaji Gopal | 2008-03-15 04:28:08 | Re: best way to run maintenance script |