Re: Proposal for changes to recovery.conf API

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(dot)paquier(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-17 00:19:43
Message-ID: CA+Tgmoa9gpqUGgRfnp5mTrKkTUo=1OVC2TrsvGQHZM7E6BBtZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 16, 2016 at 5:29 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I am fine with the release note, or the release notes plus a link to a
> wiki, like we have done in the past with complex fixes in minor
> releases:
>
> https://wiki.postgresql.org/wiki/20110408pg_upgrade_fix
>
> I think what we _don't_ want is the information _only_ in the wiki, nor
> do we want to carry around migration instructions in our docs forever.

I really don't see why we're resisting Josh's idea of putting a more
complex set of migration instructions in the documentation someplace.
Seems useful to me. Sure, we'd have to "carry" it forever, but we
could make a policy of removing migration instructions for releases
that are now EOL. And even if we didn't, it's not like extra
documentation comes with some big cost. I think a lot of users would
benefit from a substantial expansion of our documentation, not just in
this area but in many other areas as well. I bet that we could double
the size of the documentation and users would love it; the hard part
would be finding qualified people to write high-quality documentation
of all the things that aren't well-explained in the current docs.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2016-12-17 00:37:53 Re: Proposal for changes to recovery.conf API
Previous Message Michael Paquier 2016-12-16 22:30:30 Re: pg_authid.rolpassword format (was Re: Password identifiers, protocol aging and SCRAM protocol)