Re: [GENERAL] PANIC: heap_update_redo: no block

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] PANIC: heap_update_redo: no block
Date: 2006-04-01 12:34:21
Message-ID: e0ls0h$1fdi$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


"Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> wrote
>
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote
>>
>> What we should be seeing, and don't see, is an indication of a backup
>> block attached to this WAL record. Furthermore, I don't see any
>> indication of a backup block attached to *any* of the WAL records in
>> Alex's printout. The only conclusion I can draw is that he had
>> full_page_writes turned OFF, and as we have just realized that that
>> setting is completely unsafe, that is the explanation for his failure.
>>
>

According to Alex, seems the problem is not because of full_page_writes OFF

>
>> According to the discussion in pgsql-hackers, to finish this case, did
>> you
>> turn off the full_page_writes parameter? I hope the answer is "yes" ...
>>
>
> If by off you mean full_page_writes = on then yes.

Regards,
Qingqing

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tatsuo Ishii 2006-04-01 14:01:28 Re: pgpool ABORT + no transaction warning
Previous Message Nikolay Samokhvalov 2006-04-01 12:28:45 PostgreSQL makes me lie

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-04-01 13:13:01 Re: Remote PL/Java, Summary
Previous Message Thomas Hallgren 2006-04-01 10:03:24 Remote PL/Java, Summary