aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2013-07-07 15:57:24 -0400
committerBruce Momjian <bruce@momjian.us>2013-07-07 15:58:07 -0400
commitbf8d8ddc08b9573d1b6ed2ef24c83db5fef18d8c (patch)
treec92b7309e38f05f14e03b432536295e83cc7b9f6
parent9f8830dbe203e1dde3e8aea594e4a23577e4d340 (diff)
downloadpostgresql-bf8d8ddc08b9573d1b6ed2ef24c83db5fef18d8c.tar.gz
postgresql-bf8d8ddc08b9573d1b6ed2ef24c83db5fef18d8c.zip
pg_upgrade: document link options
Document that tablespaces and pg_xlog can be on different file systems for pg_upgrade --link mode. Backpatch to 9.3.
-rw-r--r--doc/src/sgml/pgupgrade.sgml3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 62856f1df81..f2d2d75af39 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -336,7 +336,8 @@ NET STOP pgsql-8.3 (<productname>PostgreSQL</> 8.3 and older used a different s
copying), 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. See <literal>pg_upgrade --help</> for a full
+ same file system. (Tablespaces and <filename>pg_xlog</> can be on
+ different file systems.) See <literal>pg_upgrade --help</> for a full
list of options.
</para>