Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit59ad246

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 whodidn't understand the PG 10 version change, so give more specificexamples.Reported-by: jim@room118solutions.comDiscussion:https://postgr.es/m/20171218213041.25744.8414@wrigleys.postgresql.orgBackpatch-through: 10
1 parent1cf1112 commit59ad246

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎doc/src/sgml/ref/pgupgrade.sgml

Lines changed: 3 additions & 3 deletions
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 tothe current major release
42-
of <productname>PostgreSQL</productname>.It is not required for minor version upgrades, e.g. from
43-
9.6.2 to9.6.3.
41+
major version upgrades, e.g. from 9.5.8 to9.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 to10.2.
4444
</para>
4545

4646
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp