Re: Remove Deprecated Exclusive Backup Mode

From: Andreas Karlsson <andreas(at)proxel(dot)se>
To: Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: David Steele <david(at)pgmasters(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Remove Deprecated Exclusive Backup Mode
Date: 2018-11-27 15:05:37
Message-ID: a50188c6-6e86-6733-3f08-826f779f608e@proxel.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/27/18 3:46 PM, Stephen Frost wrote:
> I'm concerned, seriously, that people don't have anywhere near the
> concern about the recovery side of things as they do about the backup
> side of things and that's really concerning.

I agree with your larger point, but in this case the two breakages do
not seem equal. As far as I gather the removal of recovery.conf will in
practice result in a longer downtime when your recovery scripts breaks
but not any data loss. While if we remove the exclusive backup mode then
some people's backup scripts will break and if they do not properly
monitor their backups they risk data loss.

I think we should use more caution when data loss is at stake rather
than "just" downtime. So personally I am in favor of updating the manual
with warnings (right now it does not even say if exclusive or
non-exclusive is the default) and adding a deprecation warning when
people use the exclusive mode.

Best regards,
Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-11-27 15:11:43 Re: Remove Deprecated Exclusive Backup Mode
Previous Message Stephen Frost 2018-11-27 15:02:38 Re: Remove Deprecated Exclusive Backup Mode