From: John Lister <john.lister-ps@kickstone.com>
To: pgsql-admin@postgresql.org
Subject: Re: controlling autovacuum during the day.
Date: Wed, 17 Dec 2008 15:40:36 -0000
Message-ID: <F0567BC539DF4B15AE66583CA56A6546@squarepi.com> (raw)
References: <2BB7361E57C4417A975C0474610BA4C3@squarepi.com>
<27759.1229521625@sss.pgh.pa.us>
<742A9D77A1BA4171AF52BBBF6F5F2C75@squarepi.com>
<28510.1229525243@sss.pgh.pa.us>
<C806886C1AFB4DF3B0EDB86F45DC95B4@squarepi.com>
<20081217152830.GD4453@alvh.no-ip.org>
> John Lister wrote:
>
>> 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...
>
> Maybe you're doing ALTER TABLE or something else that is blocked behind
> vacuum? Vacuum doesn't block INSERT, UPDATE or DELETE, but it can block
> other operations that want exclusive locks on the table.
>
> What Postgres version is this anyway?
Now running 8.3, but this was on 8.2.
This was just with standard updates, etc
I guess i need to turn autovacuum back on to 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
Subject: Re: controlling autovacuum during the day.
In-Reply-To: <F0567BC539DF4B15AE66583CA56A6546@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