Re: Proposal for changes to recovery.conf API
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Josh Berkus <josh@agliodbs.com>, Michael Paquier <michael.paquier@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, Abhijit Menon-Sen <ams@2ndquadrant.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2016-12-18T13:21:12Z
Lists: pgsql-hackers
On Sun, Dec 18, 2016 at 02:14:06PM +0100, Magnus Hagander wrote: > > turn > > > into another section that we keep around (whether as part of the > release > > notes, > > > or as a separate "upgrade steps" section or something). > > > > I suggest whatever we do, we place the information in a permanent > > location that isn't moved or removed. > > > > > > > > +1. Absolutely. That's a very important point. > > That is really my only point --- wherever you put it, expect it to live > there forever. > > Then in the end, it turns out we're in strong agreement :) Yes, but there was talk of adding it to the docs, then removing it in later releases --- that's what I think is a bad idea. I think it would be logical to have a sub-document underneath each major release note section with more detailed instructions. This could be done for minor releases as well where necessary. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +