X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id E0B299DC81E for ; Tue, 10 Jan 2006 20:29:22 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 27233-08 for ; Tue, 10 Jan 2006 20:29:23 -0400 (AST) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 4E9899DC994 for ; Tue, 10 Jan 2006 20:29:18 -0400 (AST) Received: from mir3-fs.mir3.com (mail.mir3.com [65.208.188.100]) by svr4.postgresql.org (Postfix) with ESMTP id EABB75AF031 for ; Wed, 11 Jan 2006 00:29:21 +0000 (GMT) Received: mir3-fs.mir3.com 172.16.1.11 from 172.16.2.68 172.16.2.68 via HTTP with MS-WebStorage 6.0.6249 Received: from archimedes.mirlogic.com by mir3-fs.mir3.com; 10 Jan 2006 16:28:06 -0800 Subject: Re: help tuning queries on large database From: Mark Lewis To: Ron Cc: pgsql-performance@postgresql.org In-Reply-To: <7.0.1.0.2.20060108160633.026bd358@earthlink.net> References: <7.0.1.0.2.20060108160633.026bd358@earthlink.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: MIR3, Inc. Date: Tue, 10 Jan 2006 16:28:06 -0800 Message-Id: <1136939286.22590.27.camel@archimedes> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-22) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.001 required=5 tests=[UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.001 X-Spam-Level: X-Archive-Number: 200601/95 X-Sequence-Number: 16573 Ron, A few days back you mentioned: > Upgrade your kernel to at least 2.6.12 > There's a known issue with earlier versions of the 2.6.x kernel and > 64b CPUs like the Opteron. See kernel.org for details. > I did some searching and couldn't find any obvious mention of this issue (I gave up after searching through the first few hundred instances of "64" in the 2.6.12 changelog). Would you mind being a little more specific about which issue you're talking about? We're about to deploy some new 16GB RAM Opteron DB servers and I'd like to check and make sure RH backported whatever the fix was to their current RHEL4 kernel. Thanks, Mark Lewis