Received: from localhost (unknown [200.46.204.183])
	by developer.postgresql.org (Postfix) with ESMTP id 94D782E0080
	for <pgsql-hackers-postgresql.org@developer.postgresql.org>;
	Fri,  6 Jun 2008 15:46:13 -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 35627-07
	for <pgsql-hackers-postgresql.org@developer.postgresql.org>;
	Fri,  6 Jun 2008 15:46:06 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.186])
	by developer.postgresql.org (Postfix) with ESMTP id 612A02E0085
	for <pgsql-hackers@postgresql.org>;
	Fri,  6 Jun 2008 15:46:08 -0300 (ADT)
Received: from pse.dyndns.org (p548F208D.dip0.t-ipconnect.de [84.143.32.141])
	by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis)
	id 0MKxQS-1K4gwv3BP2-0005nT; Fri, 06 Jun 2008 20:46:06 +0200
Received: from [192.168.0.2] (helo=[192.168.0.2])
	by pse.dyndns.org with esmtp (Exim 4.44)
	id 1K4gwu-0003Pj-Sx; Fri, 06 Jun 2008 20:46:04 +0200
Message-ID: <484985EF.8080403@pse-consulting.de>
Date: Fri, 06 Jun 2008 20:46:07 +0200
From: Andreas Pflug <pgadmin@pse-consulting.de>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
References: <Pine.GSO.4.64.0806041045520.2258@westnet.com>
	<29525.1212613052@sss.pgh.pa.us> <48472E47.7030701@dunslane.net>
	<Pine.GSO.4.64.0806042033120.3874@westnet.com>
	<20080605162400.GF16502@alvh.no-ip.org>
	<48481CBF.6040602@enterprisedb.com> <48481E3A.4010306@hagander.net>
	<Pine.GSO.4.64.0806051321360.27711@westnet.com>
	<20080605174209.GL16502@alvh.no-ip.org>
	<Pine.GSO.4.64.0806051452480.27254@westnet.com>
	<20080605212129.GI14498@yugib.highrise.ca>
	<Pine.GSO.4.64.0806051725550.10475@westnet.com>
	<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>
In-Reply-To: <1618.1212765176@sss.pgh.pa.us>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V01U2FsdGVkX1/hkd9szf1d4qxIuCKEcVcodYM4RtDmB63f4x3
	VQegC7oJfbSaBfBxnVuGHPhDoeJDh8fcPeVoFzewMWvnU0RMQe
	o4NK7S2ZdVcHVOYZxUxCQ==
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200806/309
X-Sequence-Number: 119422

Tom Lane wrote:
> I grow weary of this thread.  I will say it once more: I do not believe
> for one instant that the current formatting of postgresql.conf is the
> major impediment, or even a noticeable impediment, to producing a useful
> configuration wizard.  If you wish to prove otherwise, provide a
> complete wizard except for the parts that touch the config file, and
> I will promise to finish it.
>
> I will not read or respond to any further discussion of changing the
> config file format.  It's a waste of bandwidth.
>   

Your statement doesn't really surprise me. Apparently you kind of 
celebrate misunderstanding my point, which isn't primarily about the 
file format, but about config param accessibility via api/SQL.

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.

Regards,
Andrads