From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: mark.a.sloan@gmail.com
Subject: pg_upgrade doc uses inconsistent versions within the doc.
Date: Mon, 18 Sep 2023 20:14:04 +0000
Message-ID: <169506804412.3727336.8571753495127355296@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/pgupgrade.html
Description:
I feel like for readability the pg_upgrade doc should use the same
old_version and new_version examples when showing examples throughout the
doc page.
as an exmaple I'm looking at :
https://www.postgresql.org/docs/current/pgupgrade.html
in some places the example commands use v9.6 and v16. (see step 8)
but in other places it mixes versions v9.5 and v9.6 (see step 11 sub step 8)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, mark.a.sloan@gmail.com
Subject: Re: pg_upgrade doc uses inconsistent versions within the doc.
In-Reply-To: <169506804412.3727336.8571753495127355296@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox