Mention that pg_upgrade requires write permission in the current

directory.

Per report from Harald Armin Massa.

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 8578657039a220224ba1eb26434aa9c8c20a2ceb..0d51ae483216bddee61f18605baa898861f9d5e2 100644 (file)
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -272,7 +272,7 @@ NET STOP pgsql-8.3  (PostgreSQL 8.3 and older used a different s
     Run <application>pg_upgrade</>
  
     
-     Always run the pg_upgrade binary in the new server, not the old one.
+     Always run the pg_upgrade binary of the new server, not the old one.
      pg_upgrade requires the specification of the old and new cluster's
      data and executable (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. pg_upgrade --check will also outline any
      manual adjustments you will need to make after the migration.
+     pg_upgrade requires write permission in the current directory.