Skip to content

P
Postgres FD Implementation
Commit 981e5acd authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Move pg_upgrade doc mention of the port numbers to the same place.

parent 7aeff9f4
Show whitespace changes
Inline Side-by-side
Showing with 3 additions and 3 deletions
doc/src/sgml/pgupgrade.sgml
View file @ 981e5acd
...@@ -201,9 +201,7 @@ mv /usr/local/pgsql /usr/local/pgsql.old ...@@ -201,9 +201,7 @@ mv /usr/local/pgsql /usr/local/pgsql.old
<title>Install the new PostgreSQL binaries</title> <title>Install the new PostgreSQL binaries</title>
<para> <para>
Install the new server's binaries and support files. You can use the Install the new server's binaries and support files.
same port numbers for both clusters, typically 5432, because the old and
new clusters will not be running at the same time.
</para> </para>
<para> <para>
...@@ -340,6 +338,8 @@ pg_upgrade.exe ...@@ -340,6 +338,8 @@ pg_upgrade.exe
Obviously, no one should be accessing the clusters during the Obviously, no one should be accessing the clusters during the
upgrade. <application>pg_upgrade</> defaults to running servers upgrade. <application>pg_upgrade</> defaults to running servers
on port 50432 to avoid unintended client connections. 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.
</para> </para>
<para> <para>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment