Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 1D3D72E0035 for ; Thu, 5 Jun 2008 14:35:22 -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 29516-05 for ; Thu, 5 Jun 2008 14:35:16 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.174]) by developer.postgresql.org (Postfix) with ESMTP id 9EAF32E002F for ; Thu, 5 Jun 2008 14:35:17 -0300 (ADT) Received: from pse.dyndns.org (p548F1B4E.dip0.t-ipconnect.de [84.143.27.78]) by mrelayeu.kundenserver.de (node=mrelayeu4) with ESMTP (Nemesis) id 0ML21M-1K4JMc01mP-0000aK; Thu, 05 Jun 2008 19:35:04 +0200 Received: from [192.168.0.2] (helo=[192.168.0.2]) by pse.dyndns.org with esmtp (Exim 4.44) id 1K4JMa-0002X1-Tr; Thu, 05 Jun 2008 19:35:00 +0200 Message-ID: <484823C6.6030207@pse-consulting.de> Date: Thu, 05 Jun 2008 19:35:02 +0200 From: Andreas Pflug User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Greg Smith CC: Magnus Hagander , Heikki Linnakangas , Alvaro Herrera , pgsql-hackers@postgresql.org Subject: Re: Overhauling GUCS 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> <48472E47.7030701@dunslane.net> <20080605162400.GF16502@alvh.no-ip.org> <48481CBF.6040602@enterprisedb.com> <48481E3A.4010306@hagander.net> In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1/9QP+BtzOidu1oK/OejcbmZfA7z8Clx5fL57p zWU+SFC8eLfJ8I2jM1XYvSCR8t1ixMYiETXZXmq8BDMKA3gg3Y ltNnHTH/4xo5YY1LgRRfA== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/243 X-Sequence-Number: 119356 Greg Smith wrote: > On Thu, 5 Jun 2008, Magnus Hagander wrote: > >> We really need a "proper API" for it, and the stuff in pgAdmin isn't >> even enough to base one on. > > I would be curious to hear your opinion on whether the GUC overhaul > discussed in this thread is a useful precursor to building such a > proper API. Since I'm the guy who initially wrote that config file editing stuff, I feel somehow addressed. The answer is a clear ABSOLUTELY. - The current implementation is able to edit the file directly or through pgsql functions; any format change will affect that function immediately. - If documentation is enhanced by adding more comments in the postgresql.conf file, this won't help the editor because it can't rely on it to present help and hints to the user. It needs the comments/help in pg_settings or alike. Regards, Andreas