|
122 | 122 | <varlistentry> |
123 | 123 | <term><option>-k</option></term> |
124 | 124 | <term><option>--link</option></term> |
125 | | - <listitem><para>use hard links instead of copying files to the new cluster</para></listitem> |
| 125 | + <listitem><para>use hard links instead of copying files to the new |
| 126 | + cluster (use junction points on Windows)</para></listitem> |
126 | 127 | </varlistentry> |
127 | 128 |
|
128 | 129 | <varlistentry> |
@@ -333,7 +334,8 @@ NET STOP pgsql-8.3 (<productname>PostgreSQL</> 8.3 and older used a different s |
333 | 334 |
|
334 | 335 | <para> |
335 | 336 | If you use link mode, the upgrade will be much faster (no file |
336 | | - copying), but you will not be able to access your old cluster |
| 337 | + copying) and use less disk space, but you will not be able to access |
| 338 | + your old cluster |
337 | 339 | once you start the new cluster after the upgrade. Link mode also |
338 | 340 | requires that the old and new cluster data directories be in the |
339 | 341 | same file system. (Tablespaces and <filename>pg_xlog</> can be on |
|