During the initial ill-educated messing around I had set the
zero_damaged_pages to yes, but I'm guessing that the end result is the
same... Ill try it with the fresh copy of [the corrupt] data
What kind of a database can't deal with a bit of random values
injected into its sytem files anyways? :)
"Vic Simkus" <[EMAIL PROTECTED]> writes:
> If I'm understanding the errors correctly it seems that the corruption
> is in the system catalogs (metadata). The database does not use any
> fancy datatypes. Is there any way for me to rebuild the metadata
> manually? If I can see the leftover metadata a
If I'm understanding the errors correctly it seems that the corruption
is in the system catalogs (metadata). The database does not use any
fancy datatypes. Is there any way for me to rebuild the metadata
manually? If I can see the leftover metadata and the data minus the
missing metadata I can prob
"Vic Simkus" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED]:/var/log/postgresql$ reindexdb EPC
> NOTICE: table "pg_class" was reindexed
> reindexdb: reindexing of database "EPC" failed: ERROR: catalog is
> missing 4 attribute(s) for relid 10762
If you're really lucky, doing the reindex with ign
After doing some more reading I've come to the conclusion that I'm in
completely over my head. I got a fresh copy of the corrupt data and
am starting from the very beginning. Here's the error I get on
startup:
[EMAIL PROTECTED]:/usr/lib/postgresql/8.2/bin$ ./postgres -D
/var/lib/postgresql/8.2/
Hello
A disk hosting an instance of 8.2 crashed on me (hardware failure). I
was able to pull most of the data off the drive, but the one database
that I need the most is corrupt. I'm not really sure where to
start... so here are some error messages:
[EMAIL PROTECTED]:/var/log/postgresql$ pg_dum
