Re: Remove Deprecated Exclusive Backup Mode

David Steele <david@pgmasters.net>

From: David Steele <david@pgmasters.net>

To: Andreas Karlsson <andreas@proxel.se>, Stephen Frost <sfrost@snowman.net>, Robert Haas <robertmhaas@gmail.com>

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

Date: 2018-12-12T04:21:32Z

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 10:05 AM, Andreas Karlsson wrote:
> 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 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.

The documentation says (since 9.6):

Low level base backups can be made in a non-exclusive or an exclusive
way. The non-exclusive method is recommended and the exclusive one is
deprecated and will eventually be removed.

That seems clear enough to me.

-- 
-David
david@pgmasters.net