Content-Length: 261147 | pFad | http://github.com/postgrespro/postgres/commit/f789909b59c59a33e34feac3bed2c86f18159122

25 In pg_upgade, document that the port numbers must be different when · postgrespro/postgres@f789909 · GitHub
Skip to content

Commit f789909

Browse files
committed
In pg_upgade, document that the port numbers must be different when
checking an old running server.
1 parent 58a031f commit f789909

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

doc/src/sgml/pgupgrade.sgml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -367,8 +367,10 @@ pg_upgrade.exe
367367
Obviously, no one should be accessing the clusters during the
368368
upgrade. <application>pg_upgrade</> defaults to running servers
369369
on port 50432 to avoid unintended client connections.
370-
You can use the same port numbers for both clusters because the
371-
old and new clusters will not be running at the same time.
370+
You can use the same port number for both clusters when doing an
371+
upgrade because the old and new clusters will not be running at the
372+
same time. However, when checking an old running server, the old
373+
and new port numbers must be different.
372374
</para>
373375

374376
<para>

0 commit comments

Comments
 (0)








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/postgrespro/postgres/commit/f789909b59c59a33e34feac3bed2c86f18159122

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy