Skip site navigation (1) Skip section navigation (2)

Re: BUG #5238: frequent signal 11 segfaults

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-19 09:44:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
More info: we disabled autovacuum (we do vacuuming via cron)
and the segfaults seem to be gone.


Tom Lane wrote:
> Nagy Daniel <nagy(dot)daniel(at)telekom(dot)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

In response to


pgsql-bugs by date

Next:From: Peter EisentrautDate: 2009-12-19 22:23:30
Subject: Re: BUG #5232: plpythonu s=s.op() raises an exception
Previous:From: Ashish AnandDate: 2009-12-19 07:52:59
Subject: Re: BUG #5249: PGUSER has to be set in the console for PSQL to authenticate

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group