From: Bruce Momjian <bruce@momjian.us>
Message-Id: <200805072134.m47LYlY16758@momjian.us>
Subject: Re: order of entries in admin docs
In-Reply-To: <20080507210211.GQ20150@alvh.no-ip.org>
To: Alvaro Herrera <alvherre@commandprompt.com>
Date: Wed, 7 May 2008 17:34:47 -0400 (EDT)
CC: Scott Marlowe <scott.marlowe@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
	pgsql-docs@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Alvaro Herrera wrote:
> > > Perhaps it would be better to have prose explaining all the stuff
> > > structured like Scott proposes, and make the postgresql.conf be just a
> > > reference linking to that.  I don't think making postgresql.conf be the
> > > primary documentation is very nice.
> > 
> > So you are suggesting splitting out the postgresql.conf content into its
> > relevant sections and just linking to it?  That would work.
> 
> Yes, or something like that.  I don't think leaving _just_ the links on
> the postgresql.conf would be enough.  But a comprehensive, verbose
> explanation should be elsewhere; a short blurb and the link would remain
> on the postgresql.conf reference.

Yea, that's certainly possible, though right now we pretty much have
_all_ the information about each configuration value in one place.  We
would lose that.  Looking at the connection postgresql.conf docs:

	http://developer.postgresql.org/pgdocs/postgres/runtime-config-connection.html

There isn't much additional text except a description of each item.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +