Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id DEB3E2E004B for ; Fri, 6 Jun 2008 05:51:54 -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 46004-07 for ; Fri, 6 Jun 2008 05:51:48 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.179]) by developer.postgresql.org (Postfix) with ESMTP id DCBCC2E0045 for ; Fri, 6 Jun 2008 05:51:50 -0300 (ADT) Received: from pse.dyndns.org (p548F1B4E.dip0.t-ipconnect.de [84.143.27.78]) by mrelayeu.kundenserver.de (node=mrelayeu6) with ESMTP (Nemesis) id 0ML29c-1K4Xfo24cA-0004ht; Fri, 06 Jun 2008 10:51:49 +0200 Received: from [192.168.0.2] (helo=[192.168.0.2]) by pse.dyndns.org with esmtp (Exim 4.44) id 1K4Xfn-00034B-Jd for pgsql-hackers@postgresql.org; Fri, 06 Jun 2008 10:51:47 +0200 Message-ID: <4848FAA6.8000903@pse-consulting.de> Date: Fri, 06 Jun 2008 10:51:50 +0200 From: Andreas Pflug User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 CC: pgsql-hackers@postgresql.org Subject: Re: Overhauling GUCS References: <29525.1212613052@sss.pgh.pa.us> <48472E47.7030701@dunslane.net> <20080605162400.GF16502@alvh.no-ip.org> <48481CBF.6040602@enterprisedb.com> <48481E3A.4010306@hagander.net> <20080605174209.GL16502@alvh.no-ip.org> <20080605212129.GI14498@yugib.highrise.ca> <3F927D52-A0FD-4575-8D24-F0F70C459235@kineticode.com> In-Reply-To: <3F927D52-A0FD-4575-8D24-F0F70C459235@kineticode.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX18wW6BNvWo82KjLWjVXYUNCCiOMRt9JhNOqeg4 fUF/hJPMj7Dw5dpZ8zlT1yw9XE4UWX/90oAUQeaxCH2jl0ngEm W6HdiUAs6c0UhdNBYchVQ== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.222 tagged_above=0 required=5 tests=AWL=-1.359, MISSING_HEADERS=1.581 X-Spam-Level: X-Archive-Number: 200806/270 X-Sequence-Number: 119383 David E. Wheeler wrote: > > How about a simple rule, such as that machine-generated comments start > with "##", while user comments start with just "#"? I think that I've > seen such a rule used before. At any rate, I think that, unless you > have some sort of line marker for machine-generated comments, there > will be no way to tell them apart from user comments. Two heretical questions: Do we need user generated comments at all? I can't remember ever having used any comment in postgresql.conf. Why do so many people here insist on editing postgresql.conf as primary means of changing config params? Isn't a psql -c "SET foo=bar; MAKE PERSISTENT" just as good as sed'ing postgresql.conf or doing it manually? Looking around for different approaches, network appliances come to my mind, e.g. Cisco routers and PIX. You have 3 ways to configure a pix: - use a command line (using ssh or telnet, eqivalent to psql); WRITE MEMORY to make the changes survive a reboot. - use a web interface (or similar tool) - use tftp to up/download the complete config in and out, editing the file. User comments will be lost, with the exception of those that have been applied with special comment commands (equivalent to "comment on"). Regards, Andreas