WARNING: some databases have not been vacuumed in 1953945422 transactions - Mailing list pgsql-general

From MG
Subject WARNING: some databases have not been vacuumed in 1953945422 transactions
Date
Msg-id 001201c750d9$60016d20$340aa8c0@geisslinger
Whole thread Raw
Responses Re: WARNING: some databases have not been vacuumed in 1953945422 transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hello,
 
we are using PostgreSQL 8.0.3 and have two databases in one cluster. db1 and db2.
Each night a shell script is being executed.
 
vacuumdb --analyze -U cmduser db1
vacuumdb --analyze -U cmduser db2
 
The last weeks the following warnings are given out:
WARNING:  some databases have not been vacuumed in 1953945422 transactions
HINT:  Better vacuum them within 193538225 transactions, or you may have a wraparound failure.
 
Now I made the sql-statement:
SELECT datname, age(datfrozenxid) FROM pg_database;
 
 Yesterday I got this result: 
datname age
db11.090.080.531
db21.940.858.511
template11.940.858.511
template01.940.858.511
 
Today I got the following result:
 
datnameage
db11.075.558.667
db21.075.513.031
template11.955.716.521
template01.955.716.521
 
Why are there changes of the databases template1 and template0 ?!?
 
Is this critical?
 
Regards
Michaela

 
 

pgsql-general by date:

Previous
From: "A. Kretschmer"
Date:
Subject: Re: Installing on weendoze vista.
Next
From: RPK
Date:
Subject: Option to undo last update on table.