aboutsummaryrefslogtreecommitdiff
path: root/doc/src
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:25 -0400
commit85fa8293ad5621eaa747fbb62681b40d1b15dfa7 (patch)
treed855029021b902dc92e931a6f7480e1cf783c0fb /doc/src
parent1310d4cab21c250f666a173690671cf95eead6b7 (diff)
downloadpostgresql-85fa8293ad5621eaa747fbb62681b40d1b15dfa7.tar.gz
postgresql-85fa8293ad5621eaa747fbb62681b40d1b15dfa7.zip
pg_upgrade doc: link mode additions
Mention that link mode uses less disk space, and uses junction points on Windows. Backpatch to 9.3.
Diffstat (limited to 'doc/src')
-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 f6cd9f0d881..27d41ff57c5 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>
@@ -333,7 +334,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