Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 59ad246

Browse files
committed
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
1 parent 1cf1112 commit 59ad246

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/src/sgml/ref/pgupgrade.sgml

+3-3
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,9 @@
3838
<application>pg_upgrade</application> (formerly called <application>pg_migrator</application>) allows data
3939
stored in <productname>PostgreSQL</productname> data files to be upgraded to a later <productname>PostgreSQL</productname>
4040
major version without the data dump/reload typically required for
41-
major version upgrades, e.g. from 9.6.3 to the current major release
42-
of <productname>PostgreSQL</productname>. It is not required for minor version upgrades, e.g. from
43-
9.6.2 to 9.6.3.
41+
major version upgrades, e.g. from 9.5.8 to 9.6.4 or from 10.7 to 11.2.
42+
It is not required for minor version upgrades, e.g. from 9.6.2 to 9.6.3
43+
or from 10.1 to 10.2.
4444
</para>
4545

4646
<para>

0 commit comments

Comments
 (0)