Re: [COMMITTERS] pgsql: Move documentation of all recovery.conf option to a new chapter. - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: [COMMITTERS] pgsql: Move documentation of all recovery.conf option to a new chapter.
Date
Msg-id 4B84C783.2090408@enterprisedb.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Move documentation of all recovery.conf option to a new chapter.  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: [COMMITTERS] pgsql: Move documentation of all recovery.conf option to a new chapter.  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs wrote:
> On Mon, 2010-02-22 at 11:47 +0000, Heikki Linnakangas wrote:
>> Log Message:
>> -----------
>> Move documentation of all recovery.conf option to a new chapter.
>> They used to be scattered between the "backup and restore" and "streaming
>> replication" chapters.
> 
> It's just taken me 15 minutes to locate the settings for
> primary_conninfo to better understand Stefan's recent post.
> 
> The commit referred to here is an extremely bad change.
> 
> If you intended this to be a heading within the "High Availability"
> chapter then I would agree. This is what I thought you had done.

The idea was to have one chapter that describes all the options in
recovery.conf. Some of them are specific to streaming replication
(primary_conninfo), some are specific to PITR (recovery_target_*), some
are common (restore_command, restore_end_command). We need a reference
page to list them all.

> Having Streaming Rep described in HA and then describing the parameters
> that make it work in a separate chapter is ridiculous. Plus, wherever
> they are, they need cross references between them.

Yeah, there needs to be cross references. And the streaming rep docs
need to describe how to set the relevant settings, with examples.

> SR is a big feature and deserves proper docs.

Agreed.

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


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Alpha4 Available Now
Next
From: Pavel Stehule
Date:
Subject: Re: Issues for named/mixed function notation patch