Re: some databases have not been vacuumed ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christopher Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: some databases have not been vacuumed ...
Date: 2005-08-02 17:08:09
Message-ID: 11914.1123002489@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Christopher Browne <cbbrowne(at)acm(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Brock Williams 2005-08-02 23:59:46 FATAL: cache lookup failed for access method 6881280
Previous Message Christopher Browne 2005-08-02 14:28:52 Re: some databases have not been vacuumed ...