Re: Overhauling GUCS

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 <x> is <y>; 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