vacuum confusion - Mailing list pgsql-general

From John Sidney-Woollett
Subject vacuum confusion
Date
Msg-id 420C6076.8090607@wardbrook.com
Whole thread Raw
Responses Re: vacuum confusion  (Richard Huxton <dev@archonet.com>)
List pgsql-general
I've got a 7.4.6 db running on linux where we've been vacuuming "full"
the database each night, and have recently switched to "vacuum analyse"
instead.

We keep seeing this message at the end of the vacuum run:

WARNING:  some databases have not been vacuumed in 2013308218 transactions
HINT:  Better vacuum them within 134175429 transactions, or you may have
a wraparound failure.
VACUUM

Why are we seeing this message when the only databases in this cluster
is the one we are vacuuming (each night), and template0 and template1?

Is there something that we're not doing right?

John Sidney-Woollett

pgsql-general by date:

Previous
From: Richard Plotkin
Date:
Subject: How to fake an array of a user-defined type
Next
From: Richard Huxton
Date:
Subject: Re: vacuum confusion