From: | "Vic Simkus" <vic(dot)simkus(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Recovering database after disk crash |
Date: | 2008-05-13 01:00:28 |
Message-ID: | ce469da10805121800x409a418ev47a2cf24feef461e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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? :)
On 5/12/08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Vic Simkus" <vic(dot)simkus(at)gmail(dot)com> 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 and the data minus the
> > missing metadata I can probably piece everything together enough to
> > get the data out.
>
> Based on the evidence so far, the disk failure has zeroed out multiple,
> randomly-chosen pages of your system catalogs. I'd think it very likely
> indeed that random pages of your table files got the same favor.
> You won't have any way to know what is missing ...
>
> regards, tom lane
>
--
Men never do evil so completely and cheerfully as when they do it from
religious conviction.
-Blaise Pascal
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2008-05-13 01:20:18 | Re: rounding problems |
Previous Message | Tom Lane | 2008-05-13 00:27:59 | Re: Recovering database after disk crash |