diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
new file mode 100644
index f6cd9f0..27d41ff
*** a/doc/src/sgml/pgupgrade.sgml
--- b/doc/src/sgml/pgupgrade.sgml
***************
*** 122,128 ****
       <varlistentry>
        <term><option>-k</option></term>
        <term><option>--link</option></term>
!       <listitem><para>use hard links instead of copying files to the new cluster</para></listitem>
       </varlistentry>
  
       <varlistentry>
--- 122,129 ----
       <varlistentry>
        <term><option>-k</option></term>
        <term><option>--link</option></term>
!       <listitem><para>use hard links instead of copying files to the new
!       cluster (use junction points on Windows)</para></listitem>
       </varlistentry>
  
       <varlistentry>
*************** NET STOP pgsql-8.3  (<productname>Postgr
*** 333,339 ****
  
      <para>
       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.  (Tablespaces and <filename>pg_xlog</> can be on
--- 334,341 ----
  
      <para>
       If you use link mode, the upgrade will be much faster (no file
!      copying) and use less disk space, 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.  (Tablespaces and <filename>pg_xlog</> can be on