Re: BUG #5238: frequent signal 11 segfaults - Mailing list pgsql-bugs

From Nagy Daniel
Subject Re: BUG #5238: frequent signal 11 segfaults
Date
Msg-id 4B2CA062.3040508@telekom.hu
Whole thread Raw
In response to Re: BUG #5238: frequent signal 11 segfaults  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #5238: frequent signal 11 segfaults  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-bugs
More info: we disabled autovacuum (we do vacuuming via cron)
and the segfaults seem to be gone.

Daniel


Tom Lane wrote:
> Nagy Daniel <nagy.daniel@telekom.hu> writes:
>> 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.
>
> Hm.  Well, now that 8.4.2 is out, the first thing you ought to do is
> update and see if this happens to be resolved by any of the recent
> fixes.  (I'm not too optimistic about that, because it doesn't look
> exactly like any of the known symptoms, but an update is certainly
> worth your time in any case.)
>
> If you still see it after that, please try to extract a reproducible
> test case.
>
>             regards, tom lane

pgsql-bugs by date:

Previous
From: Ashish Anand
Date:
Subject: Re: BUG #5249: PGUSER has to be set in the console for PSQL to authenticate
Next
From: Peter Eisentraut
Date:
Subject: Re: BUG #5232: plpythonu s=s.op() raises an exception