Re: [HACKERS] Proposal for changes to recovery.conf API - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: [HACKERS] Proposal for changes to recovery.conf API
Date
Msg-id 0cbb9cb4-d736-2848-2aec-970c5e9e51e9@agliodbs.com
Whole thread Raw
In response to Re: Proposal for changes to recovery.conf API  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [HACKERS] Proposal for changes to recovery.conf API  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 12/14/2016 08:06 AM, Bruce Momjian wrote:
> On Fri, Dec  9, 2016 at 09:46:44AM +0900, Michael Paquier wrote:
>>>> My own take on it is that the release notes are already a massive
>>>> amount of work, and putting duplicative material in a bunch of other
>>>> places isn't going to make things better, it'll just increase the
>>>> maintenance burden.
>>>
>>> This would mean adding literally pages of material to the release notes.
>>> In the past, folks have been very negative on anything which would make
>>> the release notes longer.  Are you sure?
>>
>> As that's a per-version information, that seems adapted to me. There
>> could be as well in the release notes a link to the portion of the
>> docs holding this manual. Definitely this should be self-contained in
>> the docs, and not mention the wiki. My 2c.
> 
> Yes, that is the usual approach.
> 

So where in the docs should these go, then?  We don't (currently) have a
place for this kind of doc.  Appendices?

-- 
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [HACKERS] [PATCH] Remove trailing whitespaces from documentation
Next
From: Vladimir Rusinov
Date:
Subject: Re: [HACKERS] [PATCH] Remove trailing whitespaces from documentation