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-27 04:40:31
Message-ID: e07qid$1vtl$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
>
> (@)<2006-03-25 20:54:17.528 MST>[26571]LOG: REDO @ D/19176610; LSN
> D/19176644: prev D/191765E8; xid 81148979: Heap - clean: rel
> 1663/16386/16559898; b
> (@)<2006-03-25 20:54:17.528 MST>[26571]LOG: REDO @ D/19176644; LSN
> D/191766A4: prev D/19176610; xid 81148979: Heap - move: rel
> 1663/16386/16559898; ti
> (@)<2006-03-25 20:54:17.528 MST>[26571]PANIC: heap_update_redo: no
> block: target blcknum: 1, relation(1663/16386/16559898) length: 1
> (@)<2006-03-25 20:54:17.529 MST>[26570]LOG: startup process (PID
> 26571) was terminated by signal 6
>

It is like the problem due to the confliction of vacuum & update. The update
is on the page that vacuum was just removed.

Before we try to understand/attack the bug exactly, first I'd like to see
the complete xlog output. Your xlog output is imcomplete -- for example, the
first line after "b" should be "lk %u", the second line after "ti" should be
"d %u%u". Can you check out why the output looks like that? If you want to
examine the source code, look at heapam.c/heap_desc().

Regards,
Qingqing

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alex bahdushka 2006-03-27 05:03:50 Re: PANIC: heap_update_redo: no block
Previous Message Michael Fuhr 2006-03-27 04:13:57 Re: MIB for PostGReSQL

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex bahdushka 2006-03-27 05:03:50 Re: PANIC: heap_update_redo: no block
Previous Message OKADA Satoshi 2006-03-27 03:14:47 Re: Recovery from multi trouble