Date: Fri, 27 Apr 2007 11:30:33 -0400
From: Michael Stone <mstone+postgres@mathom.us>
Subject: Re: Feature Request --- was: PostgreSQL Performance Tuning
In-reply-to: <1177684612.20922.154.camel@archimedes>
To: Mark Lewis <mark.lewis@mir3.com>
Cc: pgsql-performance@postgresql.org
Mail-followup-to: Mark Lewis <mark.lewis@mir3.com>,
	pgsql-performance@postgresql.org
Message-id: <20070427153029.GB2422@mathom.us>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-disposition: inline
References: 
 <OFC96167D5.6BB63AC2-ON652572C9.003B5263-652572C9.003E4142@lntinfotech.com>
	<46310247.2050802@pinpointresearch.com> <463158DD.3060602@mochima.com>
	<2679.1177642153@sss.pgh.pa.us> <4631FA55.4010406@mochima.com>
	<20070427143023.GA2422@mathom.us>
	<1177684612.20922.154.camel@archimedes>
User-Agent: Mutt/1.5.13 (2006-08-11)

On Fri, Apr 27, 2007 at 07:36:52AM -0700, Mark Lewis wrote:
>Maybe he's looking for a switch for initdb that would make it
>interactive and quiz you about your expected usage-- sort of a magic
>auto-configurator wizard doohicky?  I could see that sort of thing being
>nice for the casual user or newbie who otherwise would have a horribly
>mis-tuned database.  They could instead have only a marginally mis-tuned
>database :)

However you implement it, anyone who can answer all of those questions 
is probably capable of reading and understanding the performance section 
in the manual. 

It's probably more practical to have a seperate script that looks at the 
running system (ram, disks, pg config, db size, indices, stats, etc.) 
and makes suggestions--if someone wants to write such a thing.

Mike Stone