Re: Proposal for changes to recovery.conf API

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, 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-18 13:11:34
Message-ID: 20161218131134.GB28523@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Dec 18, 2016 at 02:02:58PM +0100, Magnus Hagander wrote:
> >     Again, I am fine putting this as a subsection of the release notes,
> but
> >     let's not pretend it is some extra section we can remove in five
> years.
> >
> >
> > Depends on what we decide to do about it, but sure, it could certainly
> 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.

--
Bruce Momjian <bruce(at)momjian(dot)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 +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2016-12-18 13:14:06 Re: Proposal for changes to recovery.conf API
Previous Message Ryan Murphy 2016-12-18 13:04:18 Re: Trouble building uuid-ossp extension in new versions of Postgres