Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 82E702E002D for ; Thu, 5 Jun 2008 15:42:42 -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 99099-07 for ; Thu, 5 Jun 2008 15:42:37 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133]) by developer.postgresql.org (Postfix) with ESMTP id ADA572E002F for ; Thu, 5 Jun 2008 15:42:37 -0300 (ADT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m55IgZHc009843 for ; Thu, 5 Jun 2008 11:42:35 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K200060164EDM00@fe-sfbay-10.sun.com> (original mail from Robert.Lor@Sun.COM) for pgsql-hackers@postgresql.org; Thu, 05 Jun 2008 11:42:35 -0700 (PDT) Received: from [192.168.1.108] ([70.253.78.76]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K2000KZL6MFYKF0@fe-sfbay-10.sun.com>; Thu, 05 Jun 2008 11:42:16 -0700 (PDT) Date: Thu, 05 Jun 2008 13:43:08 -0500 From: Robert Lor Subject: Re: Overhauling GUCS In-reply-to: <7395.1212624912@sss.pgh.pa.us> To: Tom Lane Cc: Andreas Pflug , pgsql-hackers@postgresql.org Message-id: <484833BC.40607@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <48409D1E.3070208@agliodbs.com> <200806010032.53337.peter_e@gmx.net> <17932.1212415926@sss.pgh.pa.us> <20080604131810.GH65238@decibel.org> <4846A483.8000001@pse-consulting.de> <29525.1212613052@sss.pgh.pa.us> <48472D26.8040408@pse-consulting.de> <7395.1212624912@sss.pgh.pa.us> User-Agent: Thunderbird 2.0.0.6 (X11/20071119) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/249 X-Sequence-Number: 119362 Tom Lane wrote: > This is even assuming that the tool needs to edit the file itself, > rather than just give advice. The advice is the hard part, folks; > could we stop obsessing about trivia? +1. IMHO, the tool doesn't need to worry about generating a prettied version of postgresql.conf. It should just inform the user about the appropriate settings or create a postgresql.conf.recommend and have the user update postgresql.conf himself. -Robert