Re: Remove Deprecated Exclusive Backup Mode

David Steele <david@pgmasters.net>

From: David Steele <david@pgmasters.net>

To: Stephen Frost <sfrost@snowman.net>, Magnus Hagander <magnus@hagander.net>

Cc: Andres Freund <andres@anarazel.de>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2019-02-22T17:11:41Z

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 2/22/19 6:32 PM, Stephen Frost wrote:
> * Magnus Hagander (magnus@hagander.net) wrote:
>> On Mon, Feb 18, 2019 at 6:13 AM David Steele <david@pgmasters.net> wrote:
>>> On 2/16/19 5:57 AM, Andres Freund wrote:

>>>> I don't agree with a general 5 year deprecation window either. But it
>>>> seems pretty clear that there's no majority for removing exclusive
>>>> backups in v12.   I think it'd be good to make the warning about its
>>>> impending death more explicit, but otherwise mark this CF entry either
>>>> as rejected or returned with feedback.
>>>
>>> I think there is support for the patch in PG13 so I was planning to move
>>> it out of the March CF to the first PG13 CF as soon as the app will
>>> allow it, i.e., once there is only a single open CF.
>>
>> Agreed, and I think we should also update the documentation for 12 with the
>> suggested more explicit mention of the deprecation.
> 
> +1.

I'm working on this for the March CF.  Ideally we would back-patch it to 
9.6.

-- 
-David
david@pgmasters.net