Re: Remove Deprecated Exclusive Backup Mode - Mailing list pgsql-hackers

From David Steele
Subject Re: Remove Deprecated Exclusive Backup Mode
Date
Msg-id 8dccf18b-ce9c-4253-6309-caf38d6459a9@pgmasters.net
Whole thread Raw
In response to Re: Remove Deprecated Exclusive Backup Mode  (Christophe Pettus <xof@thebuild.com>)
List pgsql-hackers
On 2/25/19 11:20 PM, Christophe Pettus wrote:
> 
> 
>> 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
viarunbook.  Changing a runbook is institutionally less contentious, and the change is more or less "drop the file into
mumble/conf.drather than mumble", which is less of a break.
 

This is true but is becoming far less true over time.  Automation of 
recovery is now very common -- as it should be.  Backups should be 
tested regularly and recovery should not be a scary thing that is done 
at 2am from an outdated runbook.

The recovery.conf change will have serious impact when it arrives in PG12.

-- 
-David
david@pgmasters.net


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Remove Deprecated Exclusive Backup Mode
Next
From: Peter Geoghegan
Date:
Subject: Re: POC: converting Lists into arrays