Re: Remove Deprecated Exclusive Backup Mode
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Michael Paquier <michael@paquier.xyz>, Andres Freund <andres@anarazel.de>, David Steele <david@pgmasters.net>, pgsql-hackers@lists.postgresql.org
Date: 2018-11-27T15:02:38Z
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
Greetings, * Peter Eisentraut (peter.eisentraut@2ndquadrant.com) wrote: > On 27/11/2018 15:45, Stephen Frost wrote: > >>> But backup scripts are not affected by the recovery.conf changes. > >> In any of my own backup scripts (yeah!), I don't have any dependency to > >> that either. Or perhaps pgBackRest has a dependency in this area? > > If you don't consider your recovery scripts and your backup scripts to > > be related then I've really got to wonder how you're regularly testing > > your backups to make sure that they're actually valid. > > The sort of installations that continue to use the exclusive backup mode > probably have the following tooling: a 20-line shell script to make the > backup and either a 10-line shell script or a similarly sized README or > wiki page to do the recovery. Changing the latter for the recovery.conf > changes is probably a 3-line change. Changing the former for the > removal of exclusive backups would require major changes. (Try writing > a shell script that keeps a psql session open while it takes the backup > from the file system. It's possible, but it requires significantly more > logic.) They're also the sort of installations which don't have reliable backups and don't have any clue about the danger they are in due to the current bug/issue/whatever we have with exclusive backups. No, I don't agree that it's sensible to continue to march on as if nothing is wrong. Thanks! Stephen