Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id DC32C11F7E64
	for <pgsql-sql@postgresql.org>; Wed, 20 Jun 2012 01:08:29 -0300 (ADT)
Received: from mail-pz0-f46.google.com ([209.85.210.46])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ringerc@ringerc.id.au>) id 1ShCDU-0000is-GQ
	for pgsql-sql@postgresql.org; Wed, 20 Jun 2012 04:08:29 +0000
Received: by dady13 with SMTP id y13so9275798dad.19
	for <pgsql-sql@postgresql.org>; Tue, 19 Jun 2012 21:08:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding
	:x-gm-message-state;
	bh=AF3RJRfz4KbunyUzyKAN7ZxGZwbavfX5rNzWrCrMRos=;
	b=XuDtv9uusceYbwJJpL27RvjF4HPy/4UwgEqKMDj9X4BdOqQeqqPk3P5Su/Jmcj4JN6
	XNZnCXZau0qCNZBcNXj7CrbmB4yf4f6FjoQpHSf2JK4bDsy0JM9uUXN5I2mIHOEWp7zA
	hAacmbOxzHTwVTVqB4U23cfMe2kC02LhW00pWYXOJy5y9ZmLB3lq+JQzulNOMvx8KCBu
	oq0Wnlw23CiSlMbTZKG+0VMJ0eGGGdTa6iVR8K23xQC7CuLDVv8O5lRZliwuMNVZur7T
	O2nCMU1p4IdPewxeCGHx77MnmUFlahPnfvTmfdoozTg689+Hahg7agMsNfchTBAeEK2J
	MDrg==
Received: by 10.68.222.9 with SMTP id qi9mr71441632pbc.164.1340165294632;
	Tue, 19 Jun 2012 21:08:14 -0700 (PDT)
Received: from ayaki.localdomain (office1.postnewspapers.com.au.
	[150.101.171.128])
	by mx.google.com with ESMTPS id gj8sm30334199pbc.39.2012.06.19.21.08.12
	(version=SSLv3 cipher=OTHER); Tue, 19 Jun 2012 21:08:13 -0700 (PDT)
Message-ID: <4FE14CA9.8090000@ringerc.id.au>
Date: Wed, 20 Jun 2012 12:08:09 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: Achilleas Mantzios <achill@matrix.gatewaynet.com>
CC: pgsql-sql@postgresql.org
Subject: Re: Insane behaviour in 8.3.3
References: <201206141139.35601.achill@matrix.gatewaynet.com>
	<CAOR=d=36X0n0ZpDkw7VODC5TGrELCDPVj-9xJ3eAE-CWhoyvJw@mail.gmail.com>
	<201206181136.14782.achill@matrix.gatewaynet.com>
	<201206191217.49743.achill@matrix.gatewaynet.com>
In-Reply-To: <201206191217.49743.achill@matrix.gatewaynet.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: 
 ALoCoQktmJZAWz5Iwi9p1IpowtYr5Fp3RAqYnmk2GobC+al0fgyVcWW2Fy2xCvkHQax0t7poZ/UJ
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201206/56
X-Sequence-Number: 36710

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