From: Heikki Linnakangas <heikki@enterprisedb.com>
To: Steven Flatt <steven.flatt@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Database-wide VACUUM ANALYZE
Date: Thu, 21 Jun 2007 19:33:47 +0100
Message-ID: <467AC48B.2050803@enterprisedb.com> (raw)
In-Reply-To: <357fa7590706211009w2ef6071fn83c5759db6be1e80@mail.gmail.com>
References: <357fa7590706211009w2ef6071fn83c5759db6be1e80@mail.gmail.com>
Steven Flatt wrote:
> The bad thing, which I don't totally understand from reading the docs, is
> that another db-wide vacuum kicked off exactly 24 hours after the first
> db-wide vacuum kicked off, before the first one had finished. (Note that
> these vacuums seem to go through the tables alphabetically.) I managed to
> explain this to myself in that there were still rows in tables not yet
> touched by the first db-wide vacuum that could have XIDs older than
> autovacuum_freeze_max_age. Fine, so two db-wide vacuums were now taking
> place, one behind the other.
Are you sure there's no cron job starting the vacuums? 24h sounds too
good to be a coincidence, and there's no magic constant of 24h in the
autovacuum code. Besides, autovacuum can only be running one VACUUM at a
time, so there must be something else launching them.
What's your vacuuming strategy in general, before and after upgrade?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
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: heikki@enterprisedb.com, steven.flatt@gmail.com
Subject: Re: Database-wide VACUUM ANALYZE
In-Reply-To: <467AC48B.2050803@enterprisedb.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