From b2e6dfeacfdcf493073c8a7e7deadd34e4d5ea03 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 31 Jan 2018 17:09:59 -0500 Subject: [PATCH] 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 --- doc/src/sgml/ref/pgupgrade.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index 841d97c3ec..302e543e42 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -38,9 +38,9 @@ pg_upgrade (formerly called pg_migrator) allows data stored in PostgreSQL data files to be upgraded to a later 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 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. -- 2.40.0