public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: [email protected]
To: [email protected]
Subject: Re: pg_upgrade docs are confusing if PostgreSQL's versioning system/language isn't known to reader
Date: Thu, 25 Jan 2018 19:26:18 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
On Mon, Dec 18, 2017 at 09:30:41PM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.6/static/pgupgrade.html
> Description:
>
> If a reader who is unfamiliar with PostgreSQL's versioning (where 9.5 and
> 9.6 are considered major versions) reads the documentation, it is unclear if
> they need to use pg_upgrade to migrate from 9.5 to 9.6, for example.
>
> The documentation says upgrading "from 9.6.3 to the current major release"
> requires pg_upgrade, but not "from 9.6.2 to 9.6.3".
>
> The problem with that language is that the current release of PostgreSQL is
> 10. So is pg_upgrade required to upgrade from 9.6.3 to current (10) because
> 9 and 10 are major versions or because 9.6 and 10.0 are major versions? (the
> latter).
>
> It would be clearer if the documentation covered all three cases:
> 9.6.3 -> 10.0.0 and 9.5.1 -> 9.6.3: pg_upgrade should be used
> 9.6.2 -> 9.6.3: pg_upgrade not needed
>
> Or if the documentation simply noted that the second decimal is considered a
> major release.
How is this attached patch?
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
Attachments:
[text/x-diff] version.diff (848B, 2-version.diff)
download | inline diff:
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
new file mode 100644
index 055eac3..ed34a64
*** a/doc/src/sgml/ref/pgupgrade.sgml
--- b/doc/src/sgml/ref/pgupgrade.sgml
***************
*** 40,46 ****
major version without the data dump/reload typically required for
major version upgrades, e.g. from 9.6.3 to the current major release
of <productname>PostgreSQL</productname>. It is not required for minor version upgrades, e.g. from
! 9.6.2 to 9.6.3.
</para>
<para>
--- 40,46 ----
major version without the data dump/reload typically required for
major version upgrades, e.g. from 9.6.3 to the current major release
of <productname>PostgreSQL</productname>. It is not required for minor version upgrades, e.g. from
! 9.6.2 to 9.6.3 or from 10.1 to 10.2.
</para>
<para>
view thread (10+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: pg_upgrade docs are confusing if PostgreSQL's versioning system/language isn't known to reader
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox