Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id EE1882E003D for ; Fri, 6 Jun 2008 16:57: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 25943-01 for ; Fri, 6 Jun 2008 16:57:17 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from oxford.xeocode.com (87-127-95-198.no-dns-yet.enta.net [87.127.95.198]) by developer.postgresql.org (Postfix) with ESMTP id 59FE02E003A for ; Fri, 6 Jun 2008 16:57:19 -0300 (ADT) Received: from localhost ([127.0.0.1] helo=oxford.xeocode.com) by oxford.xeocode.com with esmtp (Exim 4.69) (envelope-from ) id 1K4i3m-0001WE-OS; Fri, 06 Jun 2008 20:57:14 +0100 To: "Andreas Pflug" Cc: "Tom Lane" , Subject: Re: Overhauling GUCS In-Reply-To: <484985EF.8080403@pse-consulting.de> (Andreas Pflug's message of "Fri\, 06 Jun 2008 20\:46\:07 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) X-Draft-From: ("nnimap+mail01.enterprisedb.com:INBOX.hackers" 23117) 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> <4848FAA6.8000903@pse-consulting.de> <87ej7aeuqx.fsf@oxford.xeocode.com> <4849137C.3040008@pse-consulting.de> <877id2erp6.fsf@oxford.xeocode.com> <48492356.4040506@pse-consulting.de> <1618.1212765176@sss.pgh.pa.us> <484985EF.8080403@pse-consulting.de> From: Gregory Stark Organization: EnterpriseDB Date: Fri, 06 Jun 2008 20:57:14 +0100 Message-ID: <87prqucp5x.fsf@oxford.xeocode.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/315 X-Sequence-Number: 119428 "Andreas Pflug" writes: > I personally wouldn't even think about starting such a wizard, unless I have an > idea how to push the result into the database. No, not a file, but via SQL! So > your statement you won't react unless a wizard is almost ready is prohibitive, > apart from the fact that not only wizards (featuring AI) are interesting, but > simple config tools as well. Well there's a perfectly good place to start today. Dump out a config file with the settings your wizard or config tool wants to change from their current values. We could come up with a canonical filename for such a file and include an include directive for it in the standard configuration file or you could just include instructions saying what include line to add to your config file in the installation instructions for your tool. Great, I'm glad we've resolved that issue. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning