mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

In the pg_upgrade docs, move 50432 port mention to the place where we

Browse Source 
talk about client access.
This commit is contained in:
Bruce Momjian 2011-07-01 18:36:00 -04:00
parent a88f4496b7
commit cc81d9969c
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/pgupgrade.sgml
View File

@ -302,13 +302,11 @@ NET STOP pgsql-8.3 (<productname>PostgreSQL</> 8.3 and older used a different s
copying), but you will not be able to access your old cluster copying), but you will not be able to access your old cluster
once you start the new cluster after the upgrade. Link mode also once you start the new cluster after the upgrade. Link mode also
requires that the old and new cluster data directories be in the requires that the old and new cluster data directories be in the
same file system. same file system. See <literal>pg_upgrade --help</> for a full
list of options.
</para> </para>
<para> <para>
<application>pg_upgrade</> defaults to running servers on port
50432 to avoid unintended client connections. See <literal>pg_upgrade
--help</> for a full list of options.
</para> </para>
<para> <para>
@ -339,7 +337,9 @@ pg_upgrade.exe
</para> </para>
<para> <para>
Obviously, no one should be accessing the clusters during the upgrade. 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.
</para> </para>
<para> <para>