Re: vacuum confusion

John Sidney-Woollett wrote:
> 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?

Are you doing template0/1 too? The transaction IDs are shared between
all databases AFAIK. Before the numbers wrap-around any "low" numbers
need to be replaced by a "frozen" marker (I think it's 0 or 1).

--
   Richard Huxton
   Archonet Ltd