Tom Lane wrote:
> "Qingqing Zhou" <zhouqq@cs.toronto.edu> writes:
>
>>"Jo De Haes" <jo.de_nospam_haes@indicator.be> wrote
>>
>>>CETERROR: XX001: invalid page header in block 22182 of relation
>>
>>"dunn_main"
>
>
>>I suppose there is no system error happens during the period (like lost
>>power). Can you attach the gdb at "b bufmgr.c:257" and print the content of
>>"(PageHeader) bufBlock"?
>
>
> Probably easier (especially if he's not using a debug-enabled build):
> dump out the page from the disk file using pg_filedump, or even just
> "dd | od -x".
>
Thanks for the 'easier' alternative. I tried to do this last friday,
but i was amazed when a count(*) on the table and a rerun of the query
that had caused the invalid page header error to occur just worked now.
I asked the developper to delete all imported data again an restart the
import. This import crashed again with the same error but this time on
another block.
2006-03-27 00:15:25.458 CESTERROR: XX001: invalid page header in block
48068 of relation "dunn_main"
2006-03-27 00:15:25.458 CESTCONTEXT: SQL statement "SELECT phone FROM
dunn_main WHERE source_id = $1 AND duns = $2 "
PL/pgSQL function "proc_dunn" line 29 at select into variables
2006-03-27 00:15:25.458 CESTLOCATION: ReadBuffer, bufmgr.c:257
2006-03-27 00:15:25.458 CESTSTATEMENT: SELECT proc_dunn ('J M
Darby','TA4 3BU','215517942','1','01','S',NULL,'0219',156,1
54,387166)
But again, when i do the 'SELECT proc_dunn ('J M Darby','TA4
3BU','215517942','1','01','S',NULL,'0219',156,1
54,387166)' statement now, it works without errors.
If I would like to dump block 48068 now with pg_dumpfile, how do i know
which file this block belongs to?
Jo.
