[ADMIN] Can't create a new database from dump

How can I create a entire database from a dump generated with: ./pg_dump -U postgres -F p -E UTF8 -C --inserts --column-inserts -t ... -t-v -f dumpfile.sql I could not dump the entire database because it has corrupted rows in pg_attribute. Need help. - Marcos Oliveira -- View this

[ADMIN] corrupted rows in pg_attribute deleted

-- | Postgres Version 9.0.2 | -- After a Kernel Panic in Debian 5, we found corrupted rows in pg_attribute about 2 tables. I deleted the rows and updated the pg_class.relnatts with the result of: SELECT count(*) FROM pg_att

Re: [ADMIN] corrupted rows in pg_attribute deleted

I don't have any other healthy dump of the database. That's why I'm trying to drop these tables. - Marcos Oliveira -- View this message in context: http://postgresql.1045698.n5.nabble.com/corrupted-rows-in-pg-attribute-deleted-tp4775814p4776113.html Sent from the PostgreSQL - admin mailing

Re: [ADMIN] corrupted rows in pg_attribute deleted

I'm inserting rows in pg_attribute from a old version of the table. After that, the pg_class.relnatts field is updated with the result of: select count(*) from pg_attribute where attrelid = 167017 and attnum > 0 -- returns 24 So I try do drop the table to see if it works and I get a message like th

[ADMIN] Foreign key without the column reference

I'm using Postgres 9.0.2 on Debian 5. I have a foreign key without the column reference. In pgAdminIII, when I click in the constraint object , it shows the properties pane with the Columns parameter empty. How can I fix that? - Marcos Oliveira And I still haven't found what I'm looking for...

Re: [ADMIN] corrupted rows in pg_attribute deleted

I think I managed to restore the fields that were missing. Now I got a message that references a Pk without de column reference, but the column is in pg_attribute. I guess that solving that reference could allow me to ,finaly, drop the table. How can I fix that? - Marcos Oliveira And I still

Re: [ADMIN] corrupted rows in pg_attribute deleted

I've tried that, but no success. - Marcos Oliveira And I still haven't found what I'm looking for... -- View this message in context: http://postgresql.1045698.n5.nabble.com/corrupted-rows-in-pg-attribute-deleted-tp4775814p4786262.html Sent from the PostgreSQL - admin mailing list archive at

[ADMIN] How backup an entire database, except 6 tables?

I need to backup a database except only 6 tables. I can't use the -T parameter because I have corrupted rows in pg_attribute. What's the right combination of parameters to get this backup and restore correctly? Everything I've tried still not working. - Marcos Oliveira And I still haven't fou

Re: [ADMIN] RESTORE IS TO SLOW

I'm using postgres 9.0.2 32 bits on Debian 5. The hardware is a pc with 2 GB RAM, with 2 sata disks. Well, that's what I have at the moment. The restore was started like: pg_restore -U postgres --data-only --disable-triggers -v /bck/.sql -d The pg_restore shows: pg_restore: disabling triggers fo

Re: [ADMIN] RESTORE IS TO SLOW

The dump file is in a different disk than a database. I need to have this restore finished ( it is about 80% done ) I will have to do it again, but with the changes. I will return the results to this post. - Marcos Oliveira And I still haven't found what I'm looking for... -- View this message

Re: [ADMIN] RESTORE IS TO SLOW

I'll certainly follow your advices. The log_truncate_on_rotation parameter is set to on. I figured that saves a lot of disk space in this context. this is hurting the performance? - Marcos Oliveira And I still haven't found what I'm looking for... -- View this message in context: http://post