Date: Thu, 2 Nov 2006 12:53:59 -0300
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Steven Flatt <steven.flatt@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, pgsql-performance@postgresql.org
Subject: Re: Database-wide vacuum can take a long time,
	duringwhich tables are not being analyzed
Message-ID: <20061102155359.GD25444@alvh.no-ip.org>
Mail-Followup-To: Steven Flatt <steven.flatt@gmail.com>,
	Simon Riggs <simon@2ndquadrant.com>,
	pgsql-performance@postgresql.org
References: <357fa7590611011115q748ddce9qa6cf570ec2f15348@mail.gmail.com>
	<1162464559.3587.291.camel@silverbirch.site>
	<357fa7590611020715k66ba3ba0r28c5f4511589909d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <357fa7590611020715k66ba3ba0r28c5f4511589909d@mail.gmail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)

Steven Flatt wrote:
> Sorry, I think there's a misunderstanding here.  Our system is not doing
> near that number of transactions per second.  I meant that the duration of a
> single DB-wide vacuum takes on the order of a couple of weeks.  The time
> between DB-wide vacuums is a little over a year, I believe.

I wonder if this is using some vacuum delay setting?

If that's the case, I think you could manually run a database-wide
vacuum with a zero vacuum delay setting, so that said vacuum takes less
time to finish (say, once every 8 months).

(8.2 pretty much solves this issue BTW, by not requiring database-wide
vacuums).

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