Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 21B589FB5D3 for ; Sat, 26 May 2007 09:43:42 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 18572-04 for ; Sat, 26 May 2007 09:43:26 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by postgresql.org (Postfix) with ESMTP id AF7B69FB569 for ; Sat, 26 May 2007 09:43:31 -0300 (ADT) Received: from osgiliath.mathom.us ([72.66.0.187]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JIN00G0IFCDE4U9@vms040.mailsrvcs.net> for pgsql-performance@postgresql.org; Sat, 26 May 2007 07:43:25 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by osgiliath.mathom.us (Postfix) with ESMTP id 535B87127D; Sat, 26 May 2007 08:43:17 -0400 (EDT) Received: from osgiliath.mathom.us ([127.0.0.1]) by localhost (osgiliath.home.mathom.us [127.0.0.1]) (amavisd-new, port 10024) with LMTP id E2u27A7Uplhl; Sat, 26 May 2007 08:43:16 -0400 (EDT) Received: by osgiliath.mathom.us (Postfix, from userid 1000) id D21D8714DC; Sat, 26 May 2007 08:43:15 -0400 (EDT) Date: Sat, 26 May 2007 08:43:15 -0400 From: Michael Stone Subject: Re: ECC RAM really needed? In-reply-to: <4657912B.3000508@emolecules.com> To: Craig James Cc: pgsql-performance@postgresql.org Mail-followup-to: Craig James , pgsql-performance@postgresql.org Message-id: <20070526124313.GU1785@mathom.us> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-disposition: inline X-Virus-Scanned: Debian amavisd-new at mathom.us X-Pgp-Fingerprint: 53 FF 38 00 E7 DD 0A 9C 84 52 84 C5 EE DF 7C 88 References: <4657912B.3000508@emolecules.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/555 X-Sequence-Number: 24945 On Fri, May 25, 2007 at 06:45:15PM -0700, Craig James wrote: >We're thinking of building some new servers. We bought some a while back >that have ECC (error correcting) RAM, which is absurdly expensive compared >to the same amount of non-ECC RAM. Does anyone have any real-life data >about the error rate of non-ECC RAM, and whether it matters or not? In my >long career, I've never once had a computer that corrupted memory, or at >least I never knew if it did. ...because ECC RAM will correct single bit errors. FWIW, I've seen *a lot* of single bit errors over the years. Some systems are much better about reporting than others, but any system will have occasional errors. Also, if a stick starts to go bad you'll generally be told about with ECC memory, rather than having the system just start to flake out. Mike Stone