In pg_upgrade docs, clarify that link mode uses "hard" links.

Backpatch to 9.1 and 9.0.

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index bf5f40bf5ae0d585ae455e3b8f2fb00e48be6443..8e975d8e207e7f0fda11f5bc3d492294f2945323 100644 (file)
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -91,7 +91,7 @@
      
       -k
       --link
-      link instead of copying files to new cluster
+      use hard links instead of copying files to the new cluster
      
 
      
@@ -276,14 +276,18 @@ NET STOP pgsql-8.3  (PostgreSQL 8.3 and older used a different s
     
      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
+     data and executable (bin) directories. You can also specify
      user and port values, and whether you want the data linked instead of
-     copied (the default). If you use linking, the migration will be much
-     faster (hard link data files rather than copying them), but you
-     will no longer be able to access your old cluster once you start
-     the new cluster after the upgrade.  Link mode also requires that the
-     old and new cluster data directories be in the same file system.
-     See pg_upgrade --help for a full list of options.
+     copied (the default). 
+    
+
+    
+     If you use link mode, the upgrade will be much faster (no file
+     copying), but you will not be able to access your old cluster
+     once you start the new cluster after the upgrade.  Link mode also
+     requires that the old and new cluster data directories be in the
+     same file system. See pg_upgrade --help for a full
+     list of options.