From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, David Steele <david(at)pgmasters(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Remove Deprecated Exclusive Backup Mode |
Date: | 2018-11-27 14:54:39 |
Message-ID: | 7db23b2e-25d1-4850-e633-4cf5a8d2a477@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.)
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-11-27 15:00:08 | Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 |
Previous Message | Stephen Frost | 2018-11-27 14:46:40 | Re: Remove Deprecated Exclusive Backup Mode |