Message-ID: <bd50647047caab850dbafe565ef1b1ef8d1027f0.camel@cybertec.at>
Subject: Re: Documentation does not mention that basebackup could not be
 used on newer major version
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: konkove@gmail.com, pgsql-docs@lists.postgresql.org
Date: Mon, 18 Sep 2023 22:08:30 +0200
In-Reply-To: 
 <169505094458.3727334.14380672628638785244@wrigleys.postgresql.org>
References: 
	<169505094458.3727334.14380672628638785244@wrigleys.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/bd50647047caab850dbafe565ef1b1ef8d1027f0.camel%40cybertec.at>
Precedence: bulk

On Mon, 2023-09-18 at 15:29 +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>=20
> Page: https://www.postgresql.org/docs/16/app-pgbasebackup.html
> Description:
>=20
> https://www.postgresql.org/docs/current/logical-replication.html
> Logical replication has excellent paragraph about usecases.
>=20
> These pages does not have them.
> https://www.postgresql.org/docs/current/app-pgdump.html
> https://www.postgresql.org/docs/current/app-pgbasebackup.html
>=20
> My main issue is that `pg_basebackup` page does not mention that this bac=
kup
> is compatible only with current version of database. I can not do basebac=
kup
> on v11 and restore that on v15, for example.

I think that that is amply documented by the fact that pg_basebackup is
*not* mentioned in https://www.postgresql.org/docs/current/upgrading.html .

You can't expect us to enumerate every tool that is not suitable for
upgrading.

Yours,
Laurenz Albe