| From: | Nagy Daniel <nagy(dot)daniel(at)telekom(dot)hu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #5238: frequent signal 11 segfaults |
| Date: | 2009-12-14 11:50:36 |
| Message-ID: | 4B26268C.3080209@telekom.hu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I have pg segfaults on two boxes, a DL160G6 and a DL380g5.
I've just checked their memory with memtest86+ v2.11
No errors were detected.
We also monitor the boxes via IPMI, and there are no signs
of HW failures.
Regards,
Daniel
Tom Lane wrote:
> Nagy Daniel <nagy(dot)daniel(at)telekom(dot)hu> writes:
>> I ran "select * from" on both tables. All rows were returned
>> successfully, no error logs were produced during the selects.
>
> Well, that would seem to eliminate the initial theory of on-disk
> corruption, except that these *other* symptoms that you just mentioned
> for the first time look a lot like index corruption. I concur with
> Pavel that intermittent hardware problems are looking more and more
> likely. Try a memory test first --- a patch of bad RAM could easily
> produce symptoms like this.
>
>> Apart from that, I think that pg shouldn't crash in case of
>> on-disk corruptions, but log an error message instead.
>
> There is very little that software can do to protect itself from
> flaky hardware :-(
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-12-14 17:25:44 | Re: BUG #5238: frequent signal 11 segfaults |
| Previous Message | Gerhard Lutz | 2009-12-14 07:57:23 | BUG #5242: ODBC driver v8.4.1 crashed |