Re: Possible mistake in backup documentation - Mailing list pgsql-docs

From Laurenz Albe
Subject Re: Possible mistake in backup documentation
Date
Msg-id 3e33df71449fdc083b1ed8a4dfe3ee129de59798.camel@cybertec.at
Whole thread Raw
In response to Possible mistake in backup documentation  (PG Doc comments form <noreply@postgresql.org>)
Responses Re: Possible mistake in backup documentation  (Magnus Hagander <magnus@hagander.net>)
List pgsql-docs
On Tue, 2020-09-22 at 14:17 +0000, PG Doc comments form wrote:
> In "25.3.3.2. Making An Exclusive Low-Level Backup", you said that "The
> exclusive backup method is deprecated and should be avoided. Prior to
> PostgreSQL 9.6, this was the only low-level method available, but it is now
> recommended that all users upgrade their scripts to use non-exclusive
> backups". But in the example in "25.3.6.1. Standalone Hot Backups" you use
> the exclusive version of backup command. Is it a mistake or not?

Yes, that's true.

How about the attached patch?

Perhaps that is too complicated, but I have no idea how to make it simpler.
Ceterum censeo, we should not deprecate the exclusive backup API.

Yours,
Laurenz Albe

Attachment

pgsql-docs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Please provide examples of rows from
Next
From: Magnus Hagander
Date:
Subject: Re: Possible mistake in backup documentation