Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id AC3DC62DBEB for ; Wed, 24 Feb 2010 13:52:31 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 51051-06 for ; Wed, 24 Feb 2010 17:52:21 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail137137.authsmtp.com (outmail137137.authsmtp.com [62.13.137.137]) by mail.postgresql.org (Postfix) with ESMTP id DCCD5632FC0 for ; Wed, 24 Feb 2010 13:52:20 -0400 (AST) Received: from mail-c194.authsmtp.com (mail-c194.authsmtp.com [62.13.128.121]) by punt6.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id o1OHqFvc084485; Wed, 24 Feb 2010 17:52:15 GMT Received: from [192.168.0.2] (88-110-213-69.dynamic.dsl.as9105.com [88.110.213.69]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id o1OHq7ge016808; Wed, 24 Feb 2010 17:52:07 GMT Subject: Re: Re: [COMMITTERS] pgsql: Move documentation of all recovery.conf option to a new chapter. From: Simon Riggs To: Fujii Masao Cc: Robert Haas , Heikki Linnakangas , pgsql-hackers@postgresql.org In-Reply-To: <3f0b79eb1002240159p19e135f9i2097abbf29177f1f@mail.gmail.com> References: <20100222114730.ADEC37541D0@cvs.postgresql.org> <1266967446.3752.4843.camel@ebony> <4B84C783.2090408@enterprisedb.com> <1266996685.3752.5825.camel@ebony> <603c8f071002240011t3151cc3q3e6e3ed3172b51d8@mail.gmail.com> <3f0b79eb1002240159p19e135f9i2097abbf29177f1f@mail.gmail.com> Content-Type: text/plain Date: Wed, 24 Feb 2010 17:52:06 +0000 Message-Id: <1267033926.3752.6544.camel@ebony> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit X-Server-Quench: 53915a17-216d-11df-80b9-0022640b883e X-Report-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCdxZQATClZOTQEd DAteCiN5VAwpPBRK HVkIKg5MJUcNSQVJ NksachtFagFba1xT HGQLWlREUVp7XGF/ awIfZQ1DY0tOQQdr U1ZPS01XHAJ3AVJe B2FmEx4lIgVHfnZw bQhqWXVdEkF5fEd4 E09TCG8HYzN9aWFL Bl1Qd1FdbQNKfB1D blAtXHsONCtlM3Bw LC8aFBMcBw5qYB5Y EEk+BnU3ZGc3IhMG fCVKBTo0BElXDwA0 MRFuJlkXAUMcNFk7 LVomXxofPVcbDgkW fQlXDSReOVQbVmwg CgVUFUkGDDxaR29A BVUhahlFHXRZWiNA GEZfDXkA X-Authentic-SMTP: 61633235383639.1015:706/Kp X-AuthFastPath: 255 X-Virus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/1987 X-Sequence-Number: 158330 On Wed, 2010-02-24 at 18:59 +0900, Fujii Masao wrote: > On Wed, Feb 24, 2010 at 5:11 PM, Robert Haas wrote: > > Looking at it, I think I do agree that this shouldn't be a whole > > chapter by itself. It's not nearly as high-level a concept as the > > chapters that surround it. But I do think it's good to list all the > > recovery.conf settings in one central place. The server config > > chapter looks like the best fit to me on first glance, but I wonder > > what others think? > > Umm... how about the following layout (just merge the server config and > the recovery config)? Since the way to specify a parameter is different > from postgresql.conf and recovery.conf, the section "Server Parameters" > would be required in both. > > 18. Server Configuration > 18.1. Server Parameters > 18.1.1. Setting Parameters > 18.1.2. File Locations > 18.1.3. Connections and Authentication > > 18.1.16. Short Options > 18.2. Recovery Parameters > 18.2.1. Setting Parameters > 18.2.2. Archive Recovery > 18.2.3. Recovery Target > 18.2.4. Standby Server That would be OK too, but you'd need to add lots and lots of links to ensure that each mention of the parameter goes to the definition. -- Simon Riggs www.2ndQuadrant.com