Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 756462E00C6 for ; Wed, 4 Jun 2008 11:20:23 -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 93649-03 for ; Wed, 4 Jun 2008 11:20:10 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.183]) by developer.postgresql.org (Postfix) with ESMTP id B113C2E00CF for ; Wed, 4 Jun 2008 11:20:15 -0300 (ADT) Received: from pse.dyndns.org (p548F1159.dip0.t-ipconnect.de [84.143.17.89]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1K3tq81SDJ-0005bY; Wed, 04 Jun 2008 16:19:51 +0200 Received: from [192.168.0.2] (helo=[192.168.0.2]) by pse.dyndns.org with esmtp (Exim 4.44) id 1K3tq6-0001T3-Ex; Wed, 04 Jun 2008 16:19:46 +0200 Message-ID: <4846A483.8000001@pse-consulting.de> Date: Wed, 04 Jun 2008 16:19:47 +0200 From: Andreas Pflug User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: "Decibel!" CC: Tom Lane , Greg Smith , Peter Eisentraut , pgsql-hackers@postgresql.org, Josh Berkus 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> In-Reply-To: <20080604131810.GH65238@decibel.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+gDgaZ9I3JCzu0NkJKTbJgr1Lik5vcOXkKlYA Q30bkVhHPgvBKqSm53jQfrvq11uaA7HSta3FEB1tyHfMZvPYI8 qXe25QWjQnZuDTqf8AhjA== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/142 X-Sequence-Number: 119255 Decibel! wrote: >> >> There's no reason that the server has to deal with a text file. I >> completely agree that there must be a method to change settings even if >> the database isn't running, but that method does not necessarily need to >> be a text file. If we can come up with a standard API for reading and >> writing config changes, we (or anyone else) can write any number of >> tools to deal with the settings. And once we have an API, we can provide >> a SQL interface on top of it. Once in a lifetime, a man should plant a tree, father a child, and write an editor... :-) Hiding the storage of config parameters opaquely behind an API is something I've been hating for a long time on win32. When reading this thread, I'm wondering if anybody ever saw a config file for a complex software product that was easily editable and understandable. I don't know one. If there was one, it'd be nice to know it so we can learn from it. IMHO the best compromise in machine and human readability is an XML format. It's easily decorateable with comments, easily interpreted and a pg_settings view could enhance it with even more comments, so an editor using pgsql functions (to read and write postresql.conf.xml) could be enabled to supply comprehensive help. Regards, Andreas