Re: Remove Deprecated Exclusive Backup Mode

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Magnus Hagander <magnus@hagander.net>, Stephen Frost <sfrost@snowman.net>, Laurenz Albe <laurenz.albe@cybertec.at>, David Steele <david@pgmasters.net>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2020-07-01T20:46:42Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Remove exclusive backup mode
- 39969e2a1e4d 15.0 landed

On Wed, Jul  1, 2020 at 04:36:03PM -0400, Robert Haas wrote:
> On Wed, Jul 1, 2020 at 4:29 PM Bruce Momjian <bruce@momjian.us> wrote:
> > Agreed.  I don't think three modes would help anyone.
> 
> Well, I think that if and when we remove the existing exclusive mode,
> we're going to break a bunch of people's backup scripts. I think it's
> appropriate to do that eventually, but I'm not in a big rush. Long
> deprecation periods are a feature, not a bug.

True, but we have had this marked as deprecated for a while.  Our
Postgres people who love backup technology want this improved, and our
operational people are asking for it to stay, so keeping the ability but
changing the API seems reasonable to me.  I tend to think our "love
backup technology" folks know more than our operational folks, even
though I am in the operational camp.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee