Re: Remove Deprecated Exclusive Backup Mode

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>

To: Michael Paquier <michael@paquier.xyz>

Cc: Martín Marqués <martin@2ndquadrant.com>, David Steele <david@pgmasters.net>, 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-01T05:27:48Z

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 Thu, Feb 28, 2019 at 7:51 PM Michael Paquier <michael@paquier.xyz> wrote:
> 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?

Comments on the documentation patch should be placed on the thread
linked to the documentation patch as opposed to here.

David J.