From: | "Brian E(dot) Pangburn" <bpangburn(at)nqadmin(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | transaction-wraparound data loss |
Date: | 2003-09-09 23:17:48 |
Message-ID: | DNKcnbbMve8AwsOiXTWJhA@eatel.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I run the following nightly using cron against my 7.3.3 databases:
vacuumdb -a -f -z
The other night, I got the following (db names have been changed to protect
the innocent):
Vacuuming db1
WARNING: Some databases have not been vacuumed in over 2 billion
transactions.
You may have already suffered transaction-wraparound data loss.
VACUUM
Vacuuming db2
VACUUM
Vacuuming db3
VACUUM
Vacuuming template1
VACUUM
I run this nightly and I don't think there is any way that I could have
processed 2 billion transactions in a single day. The first database "db1"
really isn't even used actively.
Could the error message have been generated in error? Is there something I
should check or do? Does this indicate that I'm going to have catastrophic
errors with one or all of my databases?
Any insights are much appreciated.
Brian E. Pangburn
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-09-09 23:19:05 | Re: enabling multibyte ... |
Previous Message | Marc G. Fournier | 2003-09-09 21:26:23 | enabling multibyte ... |