Too frequent warnings for wraparound failure - Mailing list pgsql-admin

From Milen A. Radev
Subject Too frequent warnings for wraparound failure
Date
Msg-id 42301107.6010901@securax.org
Whole thread Raw
Responses Re: Too frequent warnings for wraparound failure
Re: Too frequent warnings for wraparound failure
List pgsql-admin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

(This is a repost because the original was send when I was not
subscribed to the list and it is still not approved - sorry if you
received it already.)


I have installed a script that executes vacuumdb for all DBs in my
cluster (run by cron every night):

BEGIN------------------------------------------------
#!/bin/sh
# cron script to vacuum pgsql databases
#

PG_VACUUM_LOG=/var/log/pg_vacuum

echo Starting at `date "+%Y-%m-%d %H:%M:%S"` >> $PG_VACUUM_LOG
exec /usr/local/pgsql/bin/vacuumdb -U postgres -h localhost \
- --all --analyze >>$PG_VACUUM_LOG 2>&1

END--------------------------------------------------


I review the log every morning. In the beginning I got "wraparound
failure" warnings every third day. But from a week I got those warnings
every day. Well we have one table in one database where there are a lot
of inserts, but not that many - around 30-40 thousand per day.


Any ideas what could be cause? And is it an symptom for some kind of
failure coming?



Here is the excerpt from the log (for today and yesterday):

Starting at 2005-03-07 02:25:04
vacuumdb: vacuuming database "xxx1"
WARNING:  some databases have not been vacuumed in 1774832854 transactions
HINT:  Better vacuum them within 372650793 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx2"
WARNING:  some databases have not been vacuumed in 1774828277 transactions
HINT:  Better vacuum them within 372655370 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx3"
WARNING:  some databases have not been vacuumed in 1774893888 transactions
HINT:  Better vacuum them within 372589759 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "template1"
WARNING:  some databases have not been vacuumed in 1774909701 transactions
HINT:  Better vacuum them within 372573946 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx4"
WARNING:  some databases have not been vacuumed in 1774907572 transactions
HINT:  Better vacuum them within 372576075 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx5"
WARNING:  some databases have not been vacuumed in 1774908235 transactions
HINT:  Better vacuum them within 372575412 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx6"
WARNING:  some databases have not been vacuumed in 1774903764 transactions
HINT:  Better vacuum them within 372579883 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx7"
WARNING:  some databases have not been vacuumed in 1774905224 transactions
HINT:  Better vacuum them within 372578423 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx8"
WARNING:  some databases have not been vacuumed in 1774904273 transactions
HINT:  Better vacuum them within 372579374 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx9"
WARNING:  some databases have not been vacuumed in 1774814127 transactions
HINT:  Better vacuum them within 372669520 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx10"
VACUUM

Starting at 2005-03-08 02:25:57
vacuumdb: vacuuming database "xxx1"
WARNING:  some databases have not been vacuumed in 1744400306 transactions
HINT:  Better vacuum them within 403083341 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx2"
WARNING:  some databases have not been vacuumed in 1744361223 transactions
HINT:  Better vacuum them within 403122424 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx3"
WARNING:  some databases have not been vacuumed in 1744427176 transactions
HINT:  Better vacuum them within 403056471 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "template1"
WARNING:  some databases have not been vacuumed in 1744450173 transactions
HINT:  Better vacuum them within 403033474 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx4"
WARNING:  some databases have not been vacuumed in 1744460006 transactions
HINT:  Better vacuum them within 403023641 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx5"
WARNING:  some databases have not been vacuumed in 1744461917 transactions
HINT:  Better vacuum them within 403021730 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx6"
WARNING:  some databases have not been vacuumed in 1744465388 transactions
HINT:  Better vacuum them within 403018259 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx7"
WARNING:  some databases have not been vacuumed in 1744466073 transactions
HINT:  Better vacuum them within 403017574 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx8"
WARNING:  some databases have not been vacuumed in 1744464553 transactions
HINT:  Better vacuum them within 403019094 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx9"
WARNING:  some databases have not been vacuumed in 1744489170 transactions
HINT:  Better vacuum them within 402994477 transactions, or you may have
a wraparound failure.
VACUUM
vacuumdb: vacuuming database "xxx10"
VACUUM



- --
Milen A. Radev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCMBEHqGlhYx0/sboRAmmHAKCWvAXKRuX5k50WINymuvuniFh+VQCeIzw7
Cj0s6C7/2zindectk5/Clvk=
=f+3l
-----END PGP SIGNATURE-----

pgsql-admin by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: template1 database
Next
From: Kris Kiger
Date:
Subject: Re: Functions and transactions