Hello,
I'm not quite out of the woods yet, but I think I'm close. Here's
what I've done. There were some databases that were not effected by
the loss of the pg_clog files. I created a script than ran pg_dump
on each database while the files were missing. Then I created the
files that contained the 0x55 statuses. I ran the my pg_dump script
again with similar file names so the two sets of pg_dump files would
be sorted next to each other. I think that it's safe to say the
those files that reported exactly the same size under both runs have
intact data. The files that no data in either run are badly
damaged. This is true of two out of about three hundred databases.
Unfortunately, one of those databases is one of the five critical
ones. I'm going to work on that one further tomorrow. There are a
large number that have data only in the second run. Those I'll have
to carefully reconstruct. I still have to upgrade to the highest
version of 8.2 and fix my backup scheme.
Thank you all for your help.
Carol
