From: Bruce Momjian Date: Thu, 13 Feb 2014 10:06:22 +0000 (-0500) Subject: pg_upgrade: mention the need for tablespace snapshots in docs X-Git-Tag: REL9_4_BETA1~492 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=3f735ae831d3c249378280050b104ff751dfc668;p=postgresql 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 bb3b6a0a93..3da451cca2 100644 --- 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 . 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.