Re: Remove Deprecated Exclusive Backup Mode

David Steele <david@pgmasters.net>

From: David Steele <david@pgmasters.net>

To: Martín Marqués <martin@2ndquadrant.com>, Michael Paquier <michael@paquier.xyz>

Cc: Christophe Pettus <xof@thebuild.com>, Magnus Hagander <magnus@hagander.net>, Robert Haas <robertmhaas@gmail.com>, Fujii Masao <masao.fujii@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, Stephen Frost <sfrost@snowman.net>, Adrien NAYRAT <adrien.nayrat@anayrat.info>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2019-03-01T09:41:59Z

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 3/1/19 11:36 AM, Martín Marqués wrote:
> El jue., 28 de feb. de 2019 a la(s) 23:50, Michael Paquier
> (michael@paquier.xyz) escribió:
>>
>> On Thu, Feb 28, 2019 at 11:07:47PM -0300, Martín Marqués wrote:
>>> El 28/2/19 a las 15:13, David Steele escribió:
>>> +   <para>
>>> +     The exclusive backup method is deprecated and should be avoided in
>>> favor
>>> +     of the non-exclusive backup method or
>>> +     <application>pg_basebackup</application>.
>>> +   </para>
>>>
>>> Isn't pg_basebackup a non-exclusive backup method?
>>
>> It seems to me that it is exactly what this sentence means.  Perhaps
>> it should be splitted into two sentences for better clarity?
> 
> When I read that phrase I see 2 options: non-exclusive backups, and
> pg_basebackup. It's as if pg_basebackup wasn't included in the former
> group. It might bring some confusion.

This has been updated on the other thread and I CC'd you.

-- 
-David
david@pgmasters.net