diff options
| author | Bruce Momjian <bruce@momjian.us> | 2012-08-31 16:55:49 -0400 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2012-08-31 16:56:05 -0400 |
| commit | f789909b59c59a33e34feac3bed2c86f18159122 (patch) | |
| tree | 176950caa6336861dc00f27c21e79608a701cb61 | |
| parent | 58a031f920c225b20fdb45c1e56fe41ed7568900 (diff) | |
| download | postgresql-f789909b59c59a33e34feac3bed2c86f18159122.tar.gz postgresql-f789909b59c59a33e34feac3bed2c86f18159122.zip | |
In pg_upgade, document that the port numbers must be different when
checking an old running server.
| -rw-r--r-- | doc/src/sgml/pgupgrade.sgml | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index fcbe551e764..b62aba26418 100644 --- a/doc/src/sgml/pgupgrade.sgml +++ b/doc/src/sgml/pgupgrade.sgml @@ -367,8 +367,10 @@ pg_upgrade.exe Obviously, no one should be accessing the clusters during the upgrade. <application>pg_upgrade</> defaults to running servers on port 50432 to avoid unintended client connections. - You can use the same port numbers for both clusters because the - old and new clusters will not be running at the same time. + You can use the same port number for both clusters when doing an + upgrade because the old and new clusters will not be running at the + same time. However, when checking an old running server, the old + and new port numbers must be different. </para> <para> |