Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 52B612E0041 for ; Fri, 6 Jun 2008 17:02: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 30315-05 for ; Fri, 6 Jun 2008 17:02:48 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from vms173001pub.verizon.net (vms173001pub.verizon.net [206.46.173.1]) by developer.postgresql.org (Postfix) with ESMTP id DE66C2E003D for ; Fri, 6 Jun 2008 17:02:50 -0300 (ADT) Received: from ridley.home ([71.179.5.175]) by vms173001.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K220058K508N7QM@vms173001.mailsrvcs.net> for pgsql-hackers@postgresql.org; Fri, 06 Jun 2008 15:02:33 -0500 (CDT) Date: Fri, 06 Jun 2008 16:02:31 -0400 From: Robert Treat Subject: Re: Overhauling GUCS In-reply-to: To: pgsql-hackers@postgresql.org Cc: Greg Smith , Alvaro Herrera , Magnus Hagander , Heikki Linnakangas Message-id: <200806061602.31641.xzilla@users.sourceforge.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <20080604131810.GH65238@decibel.org> <20080605174209.GL16502@alvh.no-ip.org> User-Agent: KMail/1.9.9 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/317 X-Sequence-Number: 119430 On Thursday 05 June 2008 15:15:14 Greg Smith wrote: > (1) is in that proposal but is strictly optional as something to put in > the configuration file itself. The idea behind (2) is to enable tool > authors to have an easier way to suggest where to head for more > information. I'd like for it to be trivial for a tool to say "Suggested > value for is ; see > http://www.postgresql.org/docs/8.3/interactive/runtime-config-resource.html > for more information". I know what most of the settings I tinker with do, > but even I'd like it to be easier to find the right spot in the manual; > for newbies it's vital. You are correct that (2) isn't strictly necessary > here, but it's valuable and will be easier to wrap into this than to bolt > on later. > One idea I have been kicking around is having every guc have a anchor in the website (rahter than anchoring on parameter family). It might be enough to just populate the search bot with every guc anchored to family though... -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL