From: Alvaro Herrera <alvherre@commandprompt.com>
To: Ron St-Pierre <ron.pgsql@shaw.ca>
Cc: Gregory Stark <stark@enterprisedb.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 12 hour table vacuums
Date: Tue, 23 Oct 2007 15:23:18 -0300
Message-ID: <20071023182318.GN18013@alvh.no-ip.org> (raw)
In-Reply-To: <471E26E4.7040804@shaw.ca>
References: <471E18ED.3090704@shaw.ca>
<87y7dtokfu.fsf@oxford.xeocode.com>
<471E26E4.7040804@shaw.ca>
Ron St-Pierre wrote:
> Gregory Stark wrote:
>>> We were running autovacuum but it interfered with the updates to we
>>> shut it off.
>>
>> Was it just the I/O bandwidth? I'm surprised as your
>> vacuum_cost_delay is quite high. Manual vacuum doesn't do anything
>> differently from autovacuum, neither should interfere directly with
>> updates except by taking away I/O bandwidth.
>>
> I don't know what the problem was. I tried to exclude certain tables
> from autovacuuming, but it autovacuumed anyway.
Probably because of Xid wraparound issues. Now that you're vacuuming
weekly it shouldn't be a problem. (It's also much less of a problem in
8.2).
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
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: alvherre@commandprompt.com, ron.pgsql@shaw.ca, stark@enterprisedb.com
Subject: Re: 12 hour table vacuums
In-Reply-To: <20071023182318.GN18013@alvh.no-ip.org>
* 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