Re: PANIC: heap_update_redo: no block

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: PANIC: heap_update_redo: no block
Date: 2006-03-21 09:35:46
Message-ID: dvohju$gaf$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


""Alex bahdushka"" <bahdushka(at)gmail(dot)com> wrote
>
> Hrm... well i obviously have restored the database by now (using
> pg_resetxlog; pg_dump; initdb; pg_restore). However i did make a
> backup of the broken directory before I created the new database. If
> anyone has any thing they would like me to try to possibly help track
> down this possible bug. I would be more than glad to do it.
>

pg_resetxlog is the last resort to "avoid" the real problem. Once you reset
it, then the xlog after that some offset will not get replayed (so the
problem disappered) and possibly some data get lost :-(.

Can you patch the heap/heapam.c/heap_xlog_update() like this:

- elog(PANIC, "heap_update_redo: no block");
+ elog(PANIC, "heap_update_redo: no block: target block: %u, relation
length: %u",
+ ItemPointerGetBlockNumber(&(xlrec->target.tid)),
+ RelationGetNumberOfBlocks(reln));

And restart your database to see what's the output?

Regards,
Qingqing

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-03-21 11:50:25 Re: What's a good default encoding?
Previous Message Vlad 2006-03-21 05:29:40 "libpq.lib"

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2006-03-21 09:44:06 Re: [Pgbuildfarm-members] guppie: 64MB RAM too small?
Previous Message Pavel Stehule 2006-03-21 05:27:54 Re: SQL/XML extension