X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 732E330ED5F; Mon, 16 Jun 2003 16:31:00 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 36195-01; Mon, 16 Jun 2003 13:30:49 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by svr1.postgresql.org (Postfix) with ESMTP id 0B37430EC9E; Mon, 16 Jun 2003 13:30:49 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3125012; Mon, 16 Jun 2003 09:30:55 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: , Subject: Re: A bit OT- RE: [PERFORM] Re-ordering .CONF params ... questions for this list Date: Mon, 16 Jun 2003 09:28:07 -0700 User-Agent: KMail/1.4.3 Cc: References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200306160928.07521.josh@agliodbs.com> X-Archive-Number: 200306/117 X-Sequence-Number: 1329 Nick, > I agree... but are we the folks that the conf file needs to be made more > intuitive for? > > If the intent is to make it easier for experienced folks like ourselves who > are working with large or unusual databases to deal with PostgreSQL, then > certainly the resource usage and tuning settings should go to the top. > We'll set the other params once & never touch them again. > > On the other hand, I suspect that the majority of postgresql users play > with the other params a bit during install to get their systems working and > never touch the resource usage or tuning params ever. (And this is as it > should be, given that the defaults are reasonable for most systems.) This is a good argument. Though if you pursue it, surely you're advocating a GUI tool for PostgreSQL.conf, not that that's a bad idea ... How do other people feel about this? What options in PostgreSQL.conf do you tweak most frequently? -- Josh Berkus Aglio Database Solutions San Francisco