pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-admin@postgresql.org
Subject: Re: some databases have not been vacuumed  ...
Date: Tue, 02 Aug 2005 10:28:52 -0400
Message-ID: <m3pssw76qj.fsf@knuth.cbbrowne.com> (raw)
References: <42EE798A.5040305@lexum.umontreal.ca>
	<42EE7BA7.6030005@commandprompt.com>

In an attempt to throw the authorities off his trail, jd@commandprompt.com ("Joshua D. Drake") transmitted:
> FM wrote:
>> Hello after a vacuum full analyse I received this  :
>> WARNING:  some databases have not been vacuumed in 1805294030 transactions
>> HINT:  Better vacuum them within 342189617 transactions, or you may
>> have a wraparound failure.
>> I read that it's because i do not vacuum DB very often.
>> Now I vacuum every night but the warning remains.
>> How can I get rid of this ?
>
> Run a vacuum full on all the database.

That seems overkill.

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 can be *possible* for the issue to be with template0, if it had at
some point been open for modification.  If that is the case, it is a
good idea to:
 - Unlock template0 (via table pg_database) 
 - Run VACUUM FREEZE on template0
 - Relock it 
-- 
(format nil "~S@~S" "cbbrowne" "gmail.com")
http://linuxdatabases.info/info/slony.html
"You think you know when you can learn, are more sure when you can
write, even more when you can teach, but certain when you can
program." -- Alan Perlis



view thread (7+ messages)  latest in thread

Message-ID: <m3pssw76qj.fsf@knuth.cbbrowne.com>
Permalink:  ../m3pssw76qj.fsf@knuth.cbbrowne.com/
Also on:    postgresql.org/message-id/m3pssw76qj.fsf@knuth.cbbrowne.com

 · 

reply

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: cbbrowne@acm.org
  Subject: Re: some databases have not been vacuumed  ...
  In-Reply-To: <m3pssw76qj.fsf@knuth.cbbrowne.com>
  References: <42EE798A.5040305@lexum.umontreal.ca> <42EE7BA7.6030005@commandprompt.com> <m3pssw76qj.fsf@knuth.cbbrowne.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