From cc81d9969c6ac32f8482b3fc1a1775d212222fa7 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 1 Jul 2011 18:36:00 -0400 Subject: [PATCH] In the pg_upgrade docs, move 50432 port mention to the place where we talk about client access. --- doc/src/sgml/pgupgrade.sgml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index aa633e2d41..102ca526bb 100644 --- a/doc/src/sgml/pgupgrade.sgml +++ b/doc/src/sgml/pgupgrade.sgml @@ -302,13 +302,11 @@ NET STOP pgsql-8.3 (PostgreSQL 8.3 and older used a different s copying), but you will not be able to access your old cluster once you start the new cluster after the upgrade. Link mode also requires that the old and new cluster data directories be in the - same file system. + same file system. See pg_upgrade --help for a full + list of options. - pg_upgrade defaults to running servers on port - 50432 to avoid unintended client connections. See pg_upgrade - --help for a full list of options. @@ -339,7 +337,9 @@ pg_upgrade.exe - Obviously, no one should be accessing the clusters during the upgrade. + Obviously, no one should be accessing the clusters during the + upgrade. pg_upgrade defaults to running servers + on port 50432 to avoid unintended client connections. -- 2.40.0