| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Andreas Karlsson <andreas(at)proxel(dot)se>, Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Remove Deprecated Exclusive Backup Mode |
| Date: | 2018-12-12 04:21:32 |
| Message-ID: | 5bc2e94d-a068-8423-37f6-6e7ea6879633@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2018-12-12 04:23:02 | Re: Remove Deprecated Exclusive Backup Mode |
| Previous Message | Magnus Hagander | 2018-12-12 04:18:28 | Re: Remove Deprecated Exclusive Backup Mode |