From: | "Alex bahdushka" <bahdushka(at)gmail(dot)com> |
---|---|
To: | "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PANIC: heap_update_redo: no block |
Date: | 2006-03-31 17:20:29 |
Message-ID: | e0bf43760603310920w70956f6cx3e035dc5275fab26@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 3/31/06, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu> wrote:
>
> ""Alex bahdushka"" <bahdushka(at)gmail(dot)com> wrote
> >
> > (@)<2006-03-18 23:30:33.035 MST>[3791]PANIC: heap_update_redo: no block
> >
>
> 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.
Thanks for all your help!
From | Date | Subject | |
---|---|---|---|
Next Message | postgresql | 2006-03-31 17:36:07 | giving users access to specific databases |
Previous Message | Jason C. Leach | 2006-03-31 16:50:16 | Recovery with pg_xlog |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-31 17:48:33 | Re: WAL dirty-buffer management bug |
Previous Message | Jonah H. Harris | 2006-03-31 17:09:34 | Re: pg_class catalog question... |