rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Mention that pg_upgrade requires write permission in the current 

directory.

Per report from Harald Armin Massa.
This commit is contained in:
Bruce Momjian 2010-09-28 18:43:01 +00:00
parent 6b44b9ba56
commit ae9acb6779
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -272,7 +272,7 @@ NET STOP pgsql-8.3 (<productname>PostgreSQL</> 8.3 and older used a different s
<title>Run <application>pg_upgrade</></title>
<para>
Always run the <application>pg_upgrade</> binary in the new server, not the old one.
Always run the <application>pg_upgrade</> binary of the new server, not the old one.
<application>pg_upgrade</> requires the specification of the old and new cluster's
data and executable (<filename>bin</>) directories. You can also specify separate
user and port values, and whether you want the data linked instead of
@ -306,6 +306,7 @@ pg_upgrade.exe
to perform only the checks, even if the old server is still
running. <command>pg_upgrade --check</> will also outline any
manual adjustments you will need to make after the migration.
<command>pg_upgrade</> requires write permission in the current directory.
</para>
<para>