From 3f735ae831d3c249378280050b104ff751dfc668 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 13 Feb 2014 05:06:22 -0500
Subject: [PATCH] pg_upgrade: mention the need for tablespace snapshots in
docs
---
doc/src/sgml/pgupgrade.sgml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index bb3b6a0a933..3da451cca22 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. <filename>postmaster.pid</>, as documented in <xref
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.
</para>
<refsect2>
--
GitLab