Re: some databases have not been vacuumed ... - Mailing list pgsql-admin

From Tom Lane
Subject Re: some databases have not been vacuumed ...
Date
Msg-id 11914.1123002489@sss.pgh.pa.us
Whole thread Raw
In response to Re: some databases have not been vacuumed ...  (Christopher Browne <cbbrowne@acm.org>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: Christopher Browne
Date:
Subject: Re: some databases have not been vacuumed ...
Next
From: Brock Williams
Date:
Subject: FATAL: cache lookup failed for access method 6881280