Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] PANIC: heap_update_redo: no block

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Alex bahdushka <bahdushka(at)gmail(dot)com>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] PANIC: heap_update_redo: no block
Date: 2006-03-28 16:27:10
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> On Tue, Mar 28, 2006 at 10:07:35AM -0500, Tom Lane wrote:
>> Well, in fact we'll have correctly recreated the page, so I'm not
>> thinking that it's necessary or desirable to check this.

> Would the suggestion made in
> help
> in this regard?

That's exactly what we are debating: whether it's still necessary/useful
to make such a check, given that we now realize the failures are just
isolated bugs and not a systemic problem with truncated files.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Martijn van OosterhoutDate: 2006-03-28 16:31:33
Subject: Re: Why are default encoding conversions
Previous:From: Tom LaneDate: 2006-03-28 16:24:51
Subject: Re: Why are default encoding conversions

pgsql-general by date

Next:From: karlyDate: 2006-03-28 16:31:35
Subject: Re: FAQ 1.1
Previous:From: Scott MarloweDate: 2006-03-28 16:26:26
Subject: Re: table owner of cloned databases

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group