From: Alvaro Herrera <alvherre@commandprompt.com>
To: Steven Flatt <steven.flatt@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Database-wide vacuum can take a long time, duringwhich tables are not being analyzed
Date: Thu, 2 Nov 2006 12:53:59 -0300
Message-ID: <20061102155359.GD25444@alvh.no-ip.org> (raw)
In-Reply-To: <357fa7590611020715k66ba3ba0r28c5f4511589909d@mail.gmail.com>
References: <357fa7590611011115q748ddce9qa6cf570ec2f15348@mail.gmail.com>
<1162464559.3587.291.camel@silverbirch.site>
<357fa7590611020715k66ba3ba0r28c5f4511589909d@mail.gmail.com>
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.
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, steven.flatt@gmail.com, simon@2ndquadrant.com
Subject: Re: Database-wide vacuum can take a long time, duringwhich tables are not being analyzed
In-Reply-To: <20061102155359.GD25444@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