pg_upgrade: mention the need for tablespace snapshots in docs

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index bb3b6a0a93357010a42e1cbc98863d2cde07e465..3da451cca224ccbdafc8bd82fe9007d7295541fd 100644 (file)
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -570,9 +570,10 @@ psql --username postgres --file script.sql postgres
    changes to make it consistent.  You might want to exclude some
    files, e.g. postmaster.pid, as documented in 
    linkend="backup-lowlevel-base-backup">.  If your file system supports
-   file system snapshots or copy-on-write file copying, you can use that
-   to make a backup of the old cluster, though the snapshot and copies
-   must be created simultaneously or while the database server is down.
+   file system snapshots or copy-on-write file copies, you can use that
+   to make a backup of the old cluster and tablespaces, though the snapshot
+   and copies must be created simultaneously or while the database server
+   is down.