Re: postmaster segfault when using SELECT on a table

From: Karsten Desler <kd(at)link11(dot)de>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: postmaster segfault when using SELECT on a table
Date: 2008-04-29 11:51:40
Message-ID: 20080429115140.GI24990@soohrt.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

* Zdenek Kotala wrote:
> Karsten Desler wrote:
> >
> >I don't know much about the postgres architecture and I don't know if
> >bounds
> >checking on-disk values on a read makes a lot of sense since usually one
> >should be able to assume that there are no randomly flipped bits; but it
> >would've been nice to have a sensible log entry as to what really
> >happened.
>
> I attached backported patch from head to 8.2. You can try it. It has small
> performance penalty, but it does not crash on corrupted data.

Thank you very much! I have restored a backup of the corrupt postgres
data files on a second server and I can confirm that postmaster no
longer crashes with the patch applied.

Thanks,
Karsten

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kirill Simonov 2008-04-29 18:42:45 BUG #4132: REASSIGN OWNED fails on procedural languages
Previous Message Sam Mason 2008-04-28 12:59:09 Re: PB with postgresql 7.4