X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5318A5282E for ; Wed, 22 Jun 2005 15:08:52 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 79972-06 for ; Wed, 22 Jun 2005 18:08:06 +0000 (GMT) Received: from veggie-fuel.com (veggie-fuel.com [200.46.208.238]) by svr1.postgresql.org (Postfix) with ESMTP id 372C95283F for ; Wed, 22 Jun 2005 15:08:05 -0300 (ADT) Received: from localhost (unknown [200.46.204.144]) by veggie-fuel.com (Postfix) with ESMTP id 7542635FA89; Wed, 22 Jun 2005 18:08:06 +0000 (GMT) Received: from veggie-fuel.com ([200.46.208.238]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 77673-09; Wed, 22 Jun 2005 18:08:02 +0000 (GMT) Received: from [10.0.0.8] (71-35-20-68.phnx.qwest.net [71.35.20.68]) by veggie-fuel.com (Postfix) with ESMTP id 0432135FA88; Wed, 22 Jun 2005 18:08:02 +0000 (GMT) Subject: Re: Performance Tuning Article From: Karim Nassar Reply-To: karim.nassar@acm.org To: Frank Wiles Cc: pgsql-performance@postgresql.org In-Reply-To: <20050622095227.05938982.frank@wiles.org> References: <20050622095227.05938982.frank@wiles.org> Content-Type: text/plain Date: Wed, 22 Jun 2005 11:05:05 -0700 Message-Id: <1119463505.6816.79.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200506/442 X-Sequence-Number: 13079 On Wed, 2005-06-22 at 09:52 -0500, Frank Wiles wrote: > I've put together a short article and posted it online regarding > performance tuning PostgreSQL in general. Nice work! Some minor issues I saw: * section "Understanding the process", para 5: "Now that PostgreSQL has a plan of what it believes to be the best way to retrieve the hardware it is time to actually get it." Do you mean "retrieve the data" instead of "retrieve the hardware"? * Perhaps some examples under "Disk Configuration"? * section "Database Design and Layout", after new table layout: "Take for example the employee table above. Your probably only display active employees throughout the majority of the application..." Do you mean "You're probably only displaying"? HTH, -- Karim Nassar