aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2021-04-01 21:17:24 -0400
committerBruce Momjian <bruce@momjian.us>2021-04-01 21:17:24 -0400
commit75e66ee690ae24c546f9a7d01d99779dbb9e08f1 (patch)
tree811246564579100d6543906432a91158e6986d2b
parent89937d001294b39469790e5a583e438af2ca1235 (diff)
downloadpostgresql-75e66ee690ae24c546f9a7d01d99779dbb9e08f1.tar.gz
postgresql-75e66ee690ae24c546f9a7d01d99779dbb9e08f1.zip
doc: mention that intervening major releases can be skipped
Also mention that you should read the intervening major releases notes. This change was also applied to the website. Discussion: https://postgr.es/m/20210330144949.GA8259@momjian.us Backpatch-through: 9.6
-rw-r--r--doc/src/sgml/runtime.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 3e7db2cf6d3..bba6b21888f 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1675,9 +1675,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>