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
commit0489953f17dfb7e5b9650b04ba8c25d0d2fe77a9 (patch)
tree709c4b88bfb76a3ed06b9725b4773f2ca4520905
parent1b6961c8fec880525e5a9ca18dc8b27c5c311548 (diff)
downloadpostgresql-0489953f17dfb7e5b9650b04ba8c25d0d2fe77a9.tar.gz
postgresql-0489953f17dfb7e5b9650b04ba8c25d0d2fe77a9.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 c8b0efa9ff3..5a620d0d32c 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1707,9 +1707,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>