|
105 | 105 | <varlistentry> |
106 | 106 | <term><option>-k</option></term> |
107 | 107 | <term><option>--link</option></term> |
108 | | - <listitem><para>linkinstead of copying files to new cluster</para></listitem> |
| 108 | + <listitem><para>use hard linksinstead of copying files to the new cluster</para></listitem> |
109 | 109 | </varlistentry> |
110 | 110 |
|
111 | 111 | <varlistentry> |
@@ -293,14 +293,18 @@ NET STOP pgsql-8.3 (<productname>PostgreSQL</> 8.3 and older used a different s |
293 | 293 | <para> |
294 | 294 | Always run the <application>pg_upgrade</> binary of the new server, not the old one. |
295 | 295 | <application>pg_upgrade</> requires the specification of the old and new cluster's |
296 | | - data and executable (<filename>bin</>) directories. You can also specify separate |
| 296 | + data and executable (<filename>bin</>) directories. You can also specify |
297 | 297 | user and port values, and whether you want the data linked instead of |
298 | | - copied (the default). If you use linking, the upgrade will be much |
299 | | - faster (hard link data files rather than copying them), but you |
300 | | - will no longer be able to access your old cluster once you start |
301 | | - the new cluster after the upgrade. Link mode also requires that the |
302 | | - old and new cluster data directories be in the same file system. |
303 | | - See <literal>pg_upgrade --help</> for a full list of options. |
| 298 | + copied (the default). |
| 299 | + </para> |
| 300 | + |
| 301 | + <para> |
| 302 | + If you use link mode, the upgrade will be much faster (no file |
| 303 | + copying), but you will not be able to access your old cluster |
| 304 | + once you start the new cluster after the upgrade. Link mode also |
| 305 | + requires that the old and new cluster data directories be in the |
| 306 | + same file system. See <literal>pg_upgrade --help</> for a full |
| 307 | + list of options. |
304 | 308 | </para> |
305 | 309 |
|
306 | 310 | <para> |
|