On Thu, 2004-08-12 at 16:21, Tom Lane wrote:
>
> You could try that, but unless the db's also have identical history (in
> the sense of the same set of transaction numbers that committed) it's
> unlikely to work. I think your problem is not that pg_class is buggered
> per se, so much as that you did not have correct pg_clog data to match it.
> The data files and the log files are an interlocking whole, you can't
> just plug in one part at random.
I know your the expert and everything, but we will have to see if I can
get the data back or not. (I like a good challenge!)
A bit more research has given me some of the info I need and I now have
the buggered db up and running (although currently in a failing state -
but I'm fairly confident that I can fix that.)
> > Any other suggestions that might get the data back or should I just
> > forget it and tell them to key it again?
>
> If you did extract something from this mess, how much could you trust
> it? Not a lot, because the bad-clog problem will affect visibility of
> rows in the user tables too.
>
Only if it was a bad-clog problem. Due to the nature of that data it is
fairly easy to tell any corrupt items.
> I'm afraid you're screwed :-(. Maybe you could learn something about
> proper backup procedures though. The backup you have obviously didn't
> work well --- how did you take it exactly?
>
Actually the backup went fine, restored fine to the alternate machine,
I'm attempting to get the data back (if any) that was input between the
backup time and the crash time.
Thanks for you past and present comments (earlier posts by you to the
list have helped me with this problem)
Thx,
Drew
