Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id EB6829FBAD4 for ; Tue, 19 Jun 2007 17:09:18 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 69535-08 for ; Tue, 19 Jun 2007 17:09:12 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from locust.cns.vt.edu (locust.cns.vt.edu [198.82.169.14]) by postgresql.org (Postfix) with ESMTP id 3D30B9FB45A for ; Tue, 19 Jun 2007 17:09:15 -0300 (ADT) Received: by locust.cns.vt.edu (Postfix, from userid 986) id 2CAE2118A4B; Tue, 19 Jun 2007 16:09:14 -0400 (EDT) Date: Tue, 19 Jun 2007 16:09:14 -0400 From: Ray Stell To: Y Sidhu Cc: pgsql-performance@postgresql.org Subject: Re: PostgreSQL Configuration Tool for Dummies Message-ID: <20070619200914.GE16830@cns.vt.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/386 X-Sequence-Number: 25419 On Tue, Jun 19, 2007 at 10:49:01AM -0700, Y Sidhu wrote: > On 6/19/07, Francisco Reyes wrote: > > > >Campbell, Lance writes: > > > >> Francisco and Richard, > >> Why ask about disk or raid? How would that impact any settings in > >> postgresql.conf? > > > >If the user has 2 disks and says that he will do a lot of updates he could > >put pg_xlog in the second disk. > > > > > >---------------------------(end of broadcast)--------------------------- > >TIP 2: Don't 'kill -9' the postmaster > > > > Let's not ask about disk or raid at this level of sanity tuning. It is > important for a newbie to take the right first step. When it comes to disks, > we start talking I/O, SATA, SCSI and the varying degrees of SATA and SCSI, > and controller cards. Then we throw in RAID and the different levels > therein. Add to that, we can talk about drivers controlling these drives and > which OS is faster, more stable, etc. As you can see, a newbie would get > drowned. So, please keep it simple. I know many people on this list are > Gurus. We know you are the best in this field, but we are not and are just > trying to improve what we have. Ignoring the i/o subsystem in db configuration, there's an idea. You could request some bonnie++ output (easy to aquire) as a baseline, do your magic analysis based on this, and skip it if it is not provided with a warning. Course the magic may be harder to come by.