Re: [GENERAL] PANIC: heap_update_redo: no block

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Alex bahdushka" <bahdushka(at)gmail(dot)com>, "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] PANIC: heap_update_redo: no block
Date: 2006-03-27 22:01:49
Message-ID: 87lkuvtulu.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> I think what's happened here is that VACUUM FULL moved the only tuple
> off page 1 of the relation, then truncated off page 1, and now
> heap_update_redo is panicking because it can't find page 1 to replay the
> move. Curious that we've not seen a case like this before, because it
> seems like a generic hazard for WAL replay.

This sounds familiar

http://archives.postgresql.org/pgsql-hackers/2005-05/msg01369.php

--
greg

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-03-27 22:09:13 Re: [GENERAL] PANIC: heap_update_redo: no block
Previous Message Jonel Rienton 2006-03-27 21:45:34 Re: [Bulk] General advice on database/web applications

Browse pgsql-hackers by date

  From Date Subject
Next Message elein 2006-03-27 22:07:36 Re: Domains as Subtypes
Previous Message Tom Lane 2006-03-27 21:09:36 Re: proposal - plpgsql: execute using into