summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2013-10-05 10:18:02 -0400
committerBruce Momjian <bruce@momjian.us>2013-10-05 10:18:17 -0400
commit6f85b317d6cc4638dc88175ec4721114dab42153 (patch)
treed3bcd743ce819b2ca364830a5da744f7495a3dd1
parent3078f2143194c6247a56cf7019c206cde5c2532c (diff)
pg_upgrade doc: link mode additions
Mention that link mode uses less disk space, and uses junction points on Windows. Backpatch to 9.3.
-rw-r--r--doc/src/sgml/pgupgrade.sgml6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index c04e552bc93..e38470a739f 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -122,7 +122,8 @@
<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>
+ <listitem><para>use hard links instead of copying files to the new
+ cluster (use junction points on Windows)</para></listitem>
</varlistentry>
<varlistentry>
@@ -334,7 +335,8 @@ NET STOP pgsql-8.3 (<productname>PostgreSQL</> 8.3 and older used a different s
<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
+ 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