aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2018-01-31 17:09:59 -0500
committerBruce Momjian <bruce@momjian.us>2018-01-31 17:09:59 -0500
commitb2e6dfeacfdcf493073c8a7e7deadd34e4d5ea03 (patch)
tree1bb5c6c7374b2d13dfc6f49077d7ef789a202098
parent5b648388b832620af403ad9cafae04eee46bd49f (diff)
downloadpostgresql-b2e6dfeacfdcf493073c8a7e7deadd34e4d5ea03.tar.gz
postgresql-b2e6dfeacfdcf493073c8a7e7deadd34e4d5ea03.zip
doc: clarify major/minor pg_upgrade versions with examples
The previous docs added in PG 10 were not clear enough for someone who didn't understand the PG 10 version change, so give more specific examples. Reported-by: jim@room118solutions.com Discussion: https://postgr.es/m/20171218213041.25744.8414@wrigleys.postgresql.org Backpatch-through: 10
-rw-r--r--doc/src/sgml/ref/pgupgrade.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 841d97c3ec9..302e543e426 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -38,9 +38,9 @@
<application>pg_upgrade</> (formerly called <application>pg_migrator</>) allows data
stored in <productname>PostgreSQL</> data files to be upgraded to a later <productname>PostgreSQL</>
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</>. It is not required for minor version upgrades, e.g. from
- 9.6.2 to 9.6.3.
+ major version upgrades, e.g. from 9.5.8 to 9.6.4 or from 10.7 to 11.2.
+ 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>