| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal for changes to recovery.conf API |
| Date: | 2016-12-09 00:16:38 |
| Message-ID: | 14401.1481242598@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> On 12/01/2016 05:58 PM, Magnus Hagander wrote:
>> And in fairness, having such a "guide to changes" chapter in each
>> release probably *would* be a good idea. But it would take resources to
>> make that. The release notes are good, but having a more hand-holding
>> version explaining incompatible changes in "regular sentences" would
>> probably be quite useful to users.
> We will have enough major changes in 10.0 to warrant writing one of
> these. Maybe not as part of the official docs, but as a set of wiki
> pages or similar.
Seems to me this is exactly the release notes' turf. If you think the
release notes aren't clear enough, step right up and help improve them.
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2016-12-09 00:34:13 | Re: Proposal for changes to recovery.conf API |
| Previous Message | Josh Berkus | 2016-12-08 23:48:07 | Re: Proposal for changes to recovery.conf API |