Re: PANIC: heap_update_redo: no block - Mailing list pgsql-general

From Alex bahdushka
Subject Re: PANIC: heap_update_redo: no block
Date
Msg-id e0bf43760603221317j79910b34nad3205c29eb3778d@mail.gmail.com
Whole thread Raw
In response to Re: PANIC: heap_update_redo: no block  ("Qingqing Zhou" <zhouqq@cs.toronto.edu>)
Responses Re: PANIC: heap_update_redo: no block
List pgsql-general
On 3/21/06, Qingqing Zhou <zhouqq@cs.toronto.edu> wrote:
>
> "Tom Lane" <tgl@sss.pgh.pa.us> wrote
> >
> > While at it, you should extend the error message to include the relation
> > ID, so you have some idea which table is affected ... this is certainly
> > not a very informative message ...
> >
>
> Exactly. Please use the following version:
>
> - elog(PANIC, "heap_update_redo: no block");
> + elog(PANIC, "heap_update_redo: no block: target blcknum: %u,
> relation(%u/%u/%u) length: %u",
> +    ItemPointerGetBlockNumber(&(xlrec->target.tid)),
> +    reln->rd_node.spcNode,
> +    reln->rd_node.dbNode,
> +    reln->rd_node.relNode,
> +    RelationGetNumberOfBlocks(reln));
>
> BTW: I just realized that there is another (better) way to do so is to
> enable WAL_DEBUG in xlog.h and SET XLOG_DEBUG=true. And that's why we don't
> have much error message in xlog redo.
>

Hrm ok ill see about doing either the patch or setting wal_debug to
true (or both).  However im currently on vacation till Saturday so ill
do this first thing then and report the results back.  Thank you very
much!

> Regards,
> Qingqing
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>

pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: question about the admin contrib module and binary
Next
From: Tom Lane
Date:
Subject: Re: quirk with update a from b