|
91 | 91 | <varlistentry> |
92 | 92 | <term><option>-k</option></term> |
93 | 93 | <term><option>--link</option></term> |
94 | | - <listitem><para>linkinstead of copying files to new cluster</para></listitem> |
| 94 | + <listitem><para>use hard linksinstead of copying files to the new cluster</para></listitem> |
95 | 95 | </varlistentry> |
96 | 96 |
|
97 | 97 | <varlistentry> |
@@ -276,14 +276,18 @@ NET STOP pgsql-8.3 (<productname>PostgreSQL</> 8.3 and older used a different s |
276 | 276 | <para> |
277 | 277 | Always run the <application>pg_upgrade</> binary of the new server, not the old one. |
278 | 278 | <application>pg_upgrade</> requires the specification of the old and new cluster's |
279 | | - data and executable (<filename>bin</>) directories. You can also specify separate |
| 279 | + data and executable (<filename>bin</>) directories. You can also specify |
280 | 280 | user and port values, and whether you want the data linked instead of |
281 | | - copied (the default). If you use linking, the migration will be much |
282 | | - faster (hard link data files rather than copying them), but you |
283 | | - will no longer be able to access your old cluster once you start |
284 | | - the new cluster after the upgrade. Link mode also requires that the |
285 | | - old and new cluster data directories be in the same file system. |
286 | | - See <literal>pg_upgrade --help</> for a full list of options. |
| 281 | + copied (the default). |
| 282 | + </para> |
| 283 | + |
| 284 | + <para> |
| 285 | + If you use link mode, the upgrade will be much faster (no file |
| 286 | + copying), but you will not be able to access your old cluster |
| 287 | + once you start the new cluster after the upgrade. Link mode also |
| 288 | + requires that the old and new cluster data directories be in the |
| 289 | + same file system. See <literal>pg_upgrade --help</> for a full |
| 290 | + list of options. |
287 | 291 | </para> |
288 | 292 |
|
289 | 293 | <para> |
|