On Tue, Mar 30, 2021 at 08:30:00AM -0700, David G. Johnston wrote:
> On Tue, Mar 30, 2021 at 8:25 AM Daniel Westermann (DWE) <
> daniel.westermann@xxxxxxxxxxxxxxxx> wrote:
> The best place would be the release notes, I guess. Right at the beginning
> here:
>
> Release notes are probably a good place too but there is already a section in
> the main documentation where this needs to be added.
>
> https://www.postgresql.org/docs/current/upgrading.html
>
> Which is linked to from the main website.
>
> https://www.postgresql.org/support/versioning/
>
> An explicit sentence stating that major upgrades can skip major versions is
> needed. The document is written assuming the reading knows this, and just
> makes a few minor notes on the topic:
> e.g., "If you are upgrading across several major versions, be sure to read the
> release notes for each intervening version."
I have two patches --- one for our website, and another for our docs,
though not for the release notes specifically. The release notes do
reference this doc section though.
My idea was to link the ability to skip upgrading to intervening
versions with the need to read intervening version release notes.
--
Bruce Momjian <bruce@xxxxxxxxxx> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
diff --git a/templates/support/versioning.html b/templates/support/versioning.html
index 45c039bf..98894f1d 100644
--- a/templates/support/versioning.html
+++ b/templates/support/versioning.html
@@ -58,7 +58,9 @@ compatibility of all stored data. A dump/reload of the database or use of the
<a href="/docs/current/pgupgrade.html">pg_upgrade</a> module is required
for major upgrades. We also recommend reading the
<a href="/docs/current/upgrading.html">upgrading</a> section of the major
-version you are planning to upgrade to.
+version you are planning to upgrade to. Though you can upgrade from
+one major version to another without upgrading to intervening versions,
+you should read the major release notes of all intervening versions.
</p>
<p>
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index bf877c0e0c..001d195b8e 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1692,9 +1692,9 @@ $ <userinput>kill -INT `head -1 /usr/local/pgsql/data/postmaster.pid`</userinput
incompatibilities, so application programming changes might be required.
All user-visible changes are listed in the release notes (<xref
linkend="release"/>); pay particular attention to the section
- labeled "Migration". If you are upgrading across several major
- versions, be sure to read the release notes for each intervening
- version.
+ labeled "Migration". Though you can upgrade from one major version
+ to another without upgrading to intervening versions, you should read
+ the major release notes of all intervening versions.
</para>
<para>
