| From: | Michael Guerin <guerin(at)rentec(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: invalid page header |
| Date: | 2004-06-12 19:02:34 |
| Message-ID: | 40CB534A.8090400@rentec.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Tom Lane wrote:
>Michael Guerin <guerin(at)rentec(dot)com> writes:
>
>
>>"Dumping and reloading the table that owns this toast table would be a safer route; it would at
>>least make it real clear what damage you'd suffered."
>>
>>
>
>
>
>>Is this b/c the damaged pages would be zero'd out?
>>
>>
>
>Right, which would make vacuum happy, but you'd be missing some data.
>(Unless you're fortunate enough that there are no currently-live rows
>on the damaged page.)
>
> regards, tom lane
>
>
I tried using pg_dump and copy, but both get errors and fail. Is there
another way that I should try to export the data? Also, I sent another
post recently trying to find out how these things happen. The drives
seem to be ok, although I still need to memcheck. This is the second
corruption in a 4 day span, but I can't find any clues to why its happening.
-michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-06-12 19:38:50 | Re: invalid page header |
| Previous Message | ghaverla | 2004-06-12 00:12:18 | Re: Character encoding in database dumps |