Robert Korteweg <robert ( at ) sambalbij ( dot ) nl> writes:
>> I have a problem with a database i'm maintaining. I first noticed
>> the problem because i could not make a backup of the database i got
>> the following error:
>> pg_dump: missing pg_database entry for database "xxx"
>> I verified this by selecting the pg_database. It was indeed gone.
>> I did some more diggin and noticed that on doing a describe (\d
>> <table>) of a table i could not see any or some of the columns in
>> the table, and a few tables i also could just see the correct
>> layout. It looks random.
> This sounds suspiciously like a transaction ID wraparound problem.
Yes i read about that, but i thought this was not my problem because i
vacuumed like i thought i should.
>> The database is a very active database. It is running on Postgresql
>> 7.3. The database is getting a VACUUM FULL ANALYZE every night.
> The *entire* database ... or are you just vacuuming the user tables
> and not the system catalogs? Daily vacuuming of the catalogs should
> have prevented any such problem (unless you are managing to exceed 1
> billion transactions per day...)
VACUUM FULL ANALYZE is the exact query i do on the database every night.
I do not know if postgres will vacuum the systemtables as well with this
command. And i do not believe the database will exceed the billion
transactions a day.
I also do not see the template databases, but i do not know if this is
important.
--
"You can't reach second base, and keep your foot on first."
Groeten,
Robert
