Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id CEF499FA5D8 for ; Thu, 19 Oct 2006 14:13:07 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 74951-04 for ; Thu, 19 Oct 2006 17:12:59 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from lynet.oppetid.no (oppetid.no [80.65.51.2]) by postgresql.org (Postfix) with ESMTP id 4D7689FA2F5 for ; Thu, 19 Oct 2006 14:12:59 -0300 (ADT) Received: by lynet.oppetid.no (Postfix, from userid 1019) id 75C8B11AFAA; Thu, 19 Oct 2006 19:12:58 +0200 (CEST) Date: Thu, 19 Oct 2006 19:12:58 +0200 From: Tobias Brox To: "Jim C. Nasby" Cc: Tobias Brox , pgsql-performance@postgresql.org Subject: Re: Swappiness setting on a linux pg server Message-ID: <20061019171258.GB29574@oppetid.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: Group Nordicbet User-Agent: Mutt/1.5.9i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200610/413 X-Sequence-Number: 21542 [Jim C. Nasby - Thu at 12:00:39PM -0500] > Well, if you're buying unreliable hardware, there's not much you can > do... you're setting yourself up for problems. I'm luckily not responsible for the hardware, but my general experience tells that you never know anything about hardware reliability until the hardware actually breaks :-) It's not always so that more expensive equipment equals better equipment.