Re: Remove Deprecated Exclusive Backup Mode

Christophe Pettus <xof@thebuild.com>

From: Christophe Pettus <xof@thebuild.com>

To: Stephen Frost <sfrost@snowman.net>

Cc: Bruce Momjian <bruce@momjian.us>, Robert Haas <robertmhaas@gmail.com>, Andres Freund <andres@anarazel.de>, Fujii Masao <masao.fujii@gmail.com>, David Steele <david@pgmasters.net>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2019-02-25T21:20:21Z

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 Feb 25, 2019, at 11:24, Stephen Frost <sfrost@snowman.net> wrote:
> Aren't they going to need to make a change for v12 now anyway?
> 
> Hopefully they're regularly testing their backups by doing a restore of
> them, and dropping a recovery.conf into the directory of a v12 system
> after restore will do exactly nothing and they'll get errors complaining
> about how they need to provide a restore_command.

It varies with the installation, but backups are 100% - epsilon automated, while restores are very frequently done via runbook.  Changing a runbook is institutionally less contentious, and the change is more or less "drop the file into mumble/conf.d rather than mumble", which is less of a break.

--
-- Christophe Pettus
   xof@thebuild.com