From: Edoardo Ceccarelli <eddy@axa.it>
Cc: pgsql-performance@postgresql.org
Subject: Re: autovacuum on a -mostly- r/o table
Date: Wed, 27 Sep 2006 18:49:23 +0200
Message-ID: <451AAB93.6010602@axa.it> (raw)
In-Reply-To: <1159374712.46586.47.camel@home>
References: <451AA1FE.9050704@axa.it>
<1159374712.46586.47.camel@home>
Rod Taylor wrote:
> On Wed, 2006-09-27 at 18:08 +0200, Edoardo Ceccarelli wrote:
>
>> I have read that autovacuum cannot check to see pg load before
>> launching
>> vacuum but is there any patch about it? that would sort out the
>> problem
>> in a good and simple way.
>>
>
> In some cases the solution to high load is to vacuum the tables being
> hit the heaviest -- meaning that simply checking machine load isn't
> enough to make that decision.
>
> In fact, that high load problem is exactly why autovacuum was created in
> the first place.
>
True,
but autovacuum could check load -before- and -during- it's execution and
it could adjust himself automatically to perform more or less
aggressively depending on the difference between those two values.
Maybe with a parameter like: maximum-autovacuum-load=0.2
that would mean: "never load the machine more than 20% for the autovacuum"
...another thing is, how could autovacuum check for machine load, this
is something I cannot imagine right now...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: eddy@axa.it
Subject: Re: autovacuum on a -mostly- r/o table
In-Reply-To: <451AAB93.6010602@axa.it>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox