From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Christophe Pettus <xof(at)thebuild(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Remove Deprecated Exclusive Backup Mode |
Date: | 2019-02-25 21:40:34 |
Message-ID: | 8dccf18b-ce9c-4253-6309-caf38d6459a9@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/25/19 11:20 PM, Christophe Pettus wrote:
>
>
>> On Feb 25, 2019, at 11:24, Stephen Frost <sfrost(at)snowman(dot)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.
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(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2019-02-25 21:41:48 | Re: POC: converting Lists into arrays |
Previous Message | Magnus Hagander | 2019-02-25 21:38:36 | Re: Remove Deprecated Exclusive Backup Mode |