Skip site navigation (1) Skip section navigation (2)

Re: controlling autovacuum during the day.

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: John Lister <john(dot)lister-ps(at)kickstone(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: controlling autovacuum during the day.
Date: 2008-12-17 15:42:47
Message-ID: 20081217154247.GE4453@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-admin
John Lister wrote:
>> 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.

That doesn't help isolating the problem; 8.3 autovacuum behavior is very
different from 8.2.  Please enable it, see how it goes, and report back
if anything seems amiss.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

pgsql-admin by date

Next:From: Alvaro HerreraDate: 2008-12-17 16:31:30
Subject: Re: controlling autovacuum during the day.
Previous:From: John ListerDate: 2008-12-17 15:40:36
Subject: Re: controlling autovacuum during the day.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group