Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id BB1152E0041 for ; Fri, 6 Jun 2008 09:35:07 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 57044-05 for ; Fri, 6 Jun 2008 09:34:59 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gauss.credativ.com (gauss.credativ.com [212.112.227.254]) by developer.postgresql.org (Postfix) with ESMTP id 54FBF2E003F for ; Fri, 6 Jun 2008 09:35:04 -0300 (ADT) Received: from hawking.credativ.lan (exit.credativ.com [87.139.82.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id DB67677544; Fri, 6 Jun 2008 14:35:01 +0200 (CEST) From: Peter Eisentraut To: pgsql-hackers@postgresql.org Subject: Re: Overhauling GUCS Date: Fri, 6 Jun 2008 14:35:00 +0200 User-Agent: KMail/1.9.9 Cc: Tom Lane , Greg Smith , Andreas Pflug , Decibel! , Josh Berkus References: <48409D1E.3070208@agliodbs.com> <29525.1212613052@sss.pgh.pa.us> In-Reply-To: <29525.1212613052@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806061435.01196.peter_e@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/276 X-Sequence-Number: 119389 Am Mittwoch, 4. Juni 2008 schrieb Tom Lane: > * Can we present the config options in a more helpful way (this is 99% > a documentation problem, not a code problem)? ack > * Can we build a "configuration wizard" to tell newbies what settings > they need to tweak? Some questions to clarify this: - What settings do "newbies" (or anyone else) typically need to change? Please post a list. - What values would you set those settings to? Please provide a description for arriving at a value, which can later be transformed into code. Note that in some cases, not even the documentation provides more than handwaving help. - If we know better values, why don't we set them by default? Another orthogonal stumbling block on the way to making all of this automatic is that the surely criticial shared_buffers setting will in any useful configuration require messing around with kernel settings that no PostgreSQL tool can really help with.