Re: "invalid page header in block 597621 of relation..."error
- From: Adam Witney <awitney(at)sgul(dot)ac(dot)uk>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
- Subject: Re: "invalid page header in block 597621 of relation..."error
- Date: Wed, 23 Nov 2005 22:13:06 +0000
- Message-id: <BFAA99F2.529E1%awitney@sgul.ac.uk> <text/plain>
On 23/11/05 9:55 pm, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Adam Witney <awitney(at)sgul(dot)ac(dot)uk> writes:
>> This table is only ever COPY'd to from data files, no updates or deletes, if
>> I could find out which data file this bit comes from I could just reupload
>> that file... Is it possible to tell what the data actually is from the data
>> I sent?
>
> You might try dumping the page with "od -c" instead of "-x" and looking
> to see if there are any recognizable strings. Also try the same on the
> preceding or following pages. Or try dumping what's on the preceding
> and following pages, eg
> select * from tab where ctid = '(597620,1)';
> select * from tab where ctid = '(597620,2)';
> ...
> (run the item number up high enough to be sure you've seen all the live
> rows on the page).
>
> To get the file back in a usable state before you add more data, you'll
> want to zero the bad block out completely, and then do a VACUUM to see
> if there are any other damaged pages.
Aha, the select statements above made it easy to identify the correct file.
Whats the best way to zero the bad block? Could I not just delete that data
and reload it?
Thanks again
Adam
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Home |
Main Index |
Thread Index