| From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | Karsten Desler <kd(at)link11(dot)de> |
| 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-28 11:24:58 |
| Message-ID: | 4815B40A.8090800@sun.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
Zdenek
| Attachment | Content-Type | Size |
|---|---|---|
| pg_lzcompress.patch | text/x-patch | 4.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2008-04-28 11:31:20 | Re: postmaster segfault when using SELECT on a table |
| Previous Message | Mark Kirkwood | 2008-04-28 07:18:28 | Re: BUG #3833: Index remains when table is dropped |