Re: Remove Deprecated Exclusive Backup Mode

David Steele <david@pgmasters.net>

From: David Steele <david@pgmasters.net>

To: Simon Riggs <simon@2ndquadrant.com>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2018-11-27T15:47:05Z

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

On 11/27/18 8:56 AM, Simon Riggs wrote:
> On Tue, 27 Nov 2018 at 03:13, David Steele <david@pgmasters.net
> <mailto:david@pgmasters.net>> wrote:
>  
> 
>     The deprecated exclusive mode promises to make a difficult problem
>     simple but doesn't live up to that promise. That's why it was replaced
>     externally in 9.6 and why pg_basebackup has not used exclusive backups
>     since it was introduced in 9.2.
> 
>     Non-exclusive backups have been available since 9.6 and several
>     third-party solutions support this mode, in addition to pg_basebackup.
> 
>     The recently introduced recovery changes will break current automated
>     solutions so this seems like a good opportunity to make improvements on
>     the backup side as well.
> 
>     I'll submit a patch for the 2019-01 commitfest.
> 
> 
> -1 for removal, in this release
> 
> It's not there because anyone likes it, it's there because removing it
> is a risk
> 
> Recent changes are the reason to keep it, not a reason to remove.

How so?

-- 
-David
david@pgmasters.net