From: John Lister <john.lister-ps@kickstone.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: controlling autovacuum during the day.
Date: Wed, 17 Dec 2008 15:20:41 -0000
Message-ID: <C806886C1AFB4DF3B0EDB86F45DC95B4@squarepi.com> (raw)
References: <2BB7361E57C4417A975C0474610BA4C3@squarepi.com>
<27759.1229521625@sss.pgh.pa.us>
<742A9D77A1BA4171AF52BBBF6F5F2C75@squarepi.com>
<28510.1229525243@sss.pgh.pa.us>
> "John Lister" <john.lister-ps@kickstone.com> writes:
>> Cheers for the quick reply. I've tweaked them quite a bit, but we have
>> quite
>> a few heavily updated tables that i'd like vacuuming to keep them in
>> check.
>> Unfortunately the autovacuum does a FULL vacuum every so often locking
>> the
>> tables for quite a long time, i'd like to move these to the evening if
>> possible.
>
> Huh? Autovacuum *never* does VACUUM FULL.
bizarre... Its been turned off for a while, but from memory the autovacuum
process was causing the table it was running on to be locked - I assumed
this was an equivalent to VACUUM FULL - causing all other connections to
wait until it had finished. Could this happen another way, i thought the
other vacuum options acted passively... I'll turn it back on and see what
happens...
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-admin@postgresql.org
Cc: john.lister-ps@kickstone.com, tgl@sss.pgh.pa.us
Subject: Re: controlling autovacuum during the day.
In-Reply-To: <C806886C1AFB4DF3B0EDB86F45DC95B4@squarepi.com>
* 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