From: | gherzig(at)fmed(dot)uba(dot)ar |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: trying to repair a bad header block |
Date: | 2008-10-30 10:26:34 |
Message-ID: | 8dda6deaa85d8d37df52be5712934431.squirrel@www.webmail.fmed.uba.ar |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> On Wed, Oct 29, 2008 at 6:36 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> writes:
>>> On Wed, Oct 29, 2008 at 4:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>> If you can tolerate losing the data on that page, just zero out the
>>>> entire 8K page. dd from /dev/zero is the usual tool.
>>
>>> Would zero_damaged_pages work here? I know it's a shotgun to kill a
>>> flea, but it's also easier and safer for a lot of folks than dding a
>>> page in their table.
>>
>> It would work, but if you have any *other* damaged pages you might
>> lose more than you were expecting ...
>
> Agreed. OTOH, on slip of the fingers for a newbie with dd and the
> whole table is gone. I guess it's always a trade off.
>
>
Thanks Tom and Scott! I just use dd for simply creating big files (oh, and
once to screw up a entire disk :)
Im going to man it in order to zero out that page(s).
Wish me lucks, dudes.
Thanks!
Gerardo
From | Date | Subject | |
---|---|---|---|
Next Message | gherzig | 2008-10-30 10:28:44 | Re: trying to repair a bad header block |
Previous Message | Tom Lane | 2008-10-30 02:30:59 | Re: simple SQL query |