Re: [GENERAL] Missing database entry in pg_database

2006-01-27 Thread Robert Korteweg

Robert Korteweg wrote:

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.


Any thought? i'm about too decide to do an initdb on this database, but 
would prever too fix the problem.


--
You can't reach second base, and keep your foot on first.

Groeten,
Robert

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [GENERAL] Missing database entry in pg_database

2006-01-26 Thread Robert Korteweg

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

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


[GENERAL] Missing database entry in pg_database

2006-01-25 Thread Robert Korteweg

Hi,

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.


The database is a very active database. It is running on Postgresql 7.3. 
The database is getting a VACUUM FULL ANALYZE every night. No updates 
where made on the machine and the error did not accour after a human 
action as far as i can see.


Can someone tell me what happened here?
Can i fix my system table?
Can i still trust the other databases on the system?



--
You can't reach second base, and keep your foot on first.

Groeten,
Robert

---(end of broadcast)---
TIP 6: explain analyze is your friend


[GENERAL] System Tables

2001-03-14 Thread Robert Korteweg

Hi,

I made a list of all the system tables and there columns in an ascii
file. the only thing i am still missing is the meening of the columns :( 

Q: does anyone already have such a file with explanations to each
column?
Q: does anyone know if there is a more accurate overview than the one on
the website (it is missing a lot of columns)?

thanks in advance
Robert Korteweg
The Netherlands

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly