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

Re: Insane behaviour in 8.3.3

From: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
To: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Insane behaviour in 8.3.3
Date: 2012-06-20 04:08:09
Message-ID: 4FE14CA9.8090000@ringerc.id.au (view raw or flat)
Thread:
Lists: pgsql-sql
On 06/19/2012 05:17 PM, Achilleas Mantzios wrote:
> We had another corruption incident on the very same machine, this time in the jboss subsystem (a "jar cvf" produced corrupted .jar).
> IMHO this means faulty RAM/disk.
> If that is true, then i guess HW sanity checks are even more important than SW upgrades.

... and a lot more difficult :S

Log monitoring is often the most imporant part - monitoring for NMIs and 
other hardware notifications, checking the kernel log for odd issues or 
reports of unexpected segfaults from userspace programs, etc.

--
Craig Ringer

In response to

Responses

pgsql-sql by date

Next:From: Achilleas MantziosDate: 2012-06-20 05:54:01
Subject: Re: Insane behaviour in 8.3.3
Previous:From: Achilleas MantziosDate: 2012-06-19 09:17:49
Subject: Re: Insane behaviour in 8.3.3

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