Message-ID: <4B8577EB.8000802@enterprisedb.com>
Date: Wed, 24 Feb 2010 21:03:07 +0200
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Organization: EnterpriseDB
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706)
MIME-Version: 1.0
To: Simon Riggs <simon@2ndQuadrant.com>
CC: pgsql-hackers@postgresql.org
Subject: Re: [COMMITTERS] pgsql: Move documentation of all recovery.conf
 option
	to a new chapter.
References: <20100222114730.ADEC37541D0@cvs.postgresql.org>	
	<1266967446.3752.4843.camel@ebony>
	<4B84C783.2090408@enterprisedb.com>	
	<1266996685.3752.5825.camel@ebony>
	<1267003260.3752.6012.camel@ebony>	
	<4B85621B.2070308@enterprisedb.com>
	<1267033689.3752.6536.camel@ebony>	
	<4B856DF1.6030004@enterprisedb.com>
	<1267037636.3752.6632.camel@ebony>
In-Reply-To: <1267037636.3752.6632.camel@ebony>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Simon Riggs wrote:
> Which is why, in the next paragraph, I proposed a way forwards...

Oh, sorry.

> There are 3 use cases: PITR, file-based replication and streaming
> replication. Having 3 separate sections would be less confusing since it
> would allow focused examples. A final section could be the "master
> reference" for defining those parameters. So having both separate and
> combined sections may end up being less confusing.

Isn't that pretty much what we have now, except that both file-based
replication and streaming replication are under the HA section? Can you
lay out a tree of the section titles you're suggesting?

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com