Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Tue, 29 Apr 2008 13:51:40 +0200
- Message-id: <20080429115140(dot)GI24990(at)soohrt(dot)org>
* 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
- References:
- postmaster segfault when using SELECT on a table
- From: Karsten Desler
- Re: postmaster segfault when using SELECT on a table
- From: Tom Lane
- Re: postmaster segfault when using SELECT on a table
- From: Karsten Desler
- Re: postmaster segfault when using SELECT on a table
- From: Zdenek Kotala
- postmaster segfault when using SELECT on a table
- Prev by Date: Re: PB with postgresql 7.4
- Next by Date: BUG #4132: REASSIGN OWNED fails on procedural languages
- Previous by thread: Re: postmaster segfault when using SELECT on a table
- Next by thread: Re: BUG #3833: Index remains when table is dropped
- Indexes: