diff options
| author | Bruce Momjian | 2010-09-28 18:43:01 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2010-09-28 18:43:01 +0000 |
| commit | ae9acb677950cf2afa037349b73fa3351d6e1d31 (patch) | |
| tree | cde400405638ae53f3d3acf1079e1c546557d3bc /doc/src | |
| parent | 6b44b9ba56e02d63425a8d950ef141bb007745ff (diff) | |
Mention that pg_upgrade requires write permission in the current
directory.
Per report from Harald Armin Massa.
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/pgupgrade.sgml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index 47c7bf6b77b..6d2cdaa335a 100644 --- a/doc/src/sgml/pgupgrade.sgml +++ b/doc/src/sgml/pgupgrade.sgml @@ -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> |