Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
To: Peter Eisentraut <peter_e@gmx.net>, pgsql-docs@postgresql.org
Subject: Re: PostgreSQL.conf / runtime docs
Date: Mon, 9 Aug 2004 13:53:59 -0700
User-Agent: KMail/1.4.3
References: <200408060942.25604.josh@agliodbs.com>
	<200408091940.25004.peter_e@gmx.net>
In-Reply-To: <200408091940.25004.peter_e@gmx.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200408091353.59483.josh@agliodbs.com>

Peter,

> If you plan to do major outline reorganizations, I suggest that you do
> them somewhat sooner than a few days before release, because there is
> also a release management effort involved in the documentation.  But
> you can always plug in your latest measurements any time.

No massive re-org, we did that last version.

No, here's what I want to do:

1) add a new section at the top of the docs describing the most common options 
that people want to set on a new installation.
2) Add notes to each item about how to decide what to set it at.
3) Add label/values for:
	Default Value:
	Set At: (when you can change it)
	(this latter information is there but buried in the text; it would be better 	
	put on a seperate line)
4) add notes regarding version changes (like that work_mem used to be 
sort_mem, and that add_missing_from will default to "false" next version)

Your recommendations on tagging stuff are highly welcome; I'm still 
uncomfortable with SGML.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco