From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christopher Browne <cbbrowne@acm.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: some databases have not been vacuumed ...
Date: Tue, 02 Aug 2005 13:08:09 -0400
Message-ID: <11914.1123002489@sss.pgh.pa.us> (raw)
In-Reply-To: <m3pssw76qj.fsf@knuth.cbbrowne.com>
References: <42EE798A.5040305@lexum.umontreal.ca>
<42EE7BA7.6030005@commandprompt.com>
<m3pssw76qj.fsf@knuth.cbbrowne.com>
Christopher Browne <cbbrowne@acm.org> writes:
> The problem is likely that the "old tuples" are in some database not
> being vacuumed. template1 is a likely candidate; do a plain VACUUM on
> that and the message may go away.
It's not really necessary to guess about which database(s) are
triggering the message: a quick look in pg_database will tell you.
See TFM:
http://www.postgresql.org/docs/8.0/static/maintenance.html#VACUUM-FOR-WRAPAROUND
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, cbbrowne@acm.org
Subject: Re: some databases have not been vacuumed ...
In-Reply-To: <11914.1123002489@sss.pgh.pa.us>
References: <42EE798A.5040305@lexum.umontreal.ca> <42EE7BA7.6030005@commandprompt.com> <m3pssw76qj.fsf@knuth.cbbrowne.com> <11914.1123002489@sss.pgh.pa.us>
* 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