From bcec58cf1ebf20ea237be042d3ef774f887557a9 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 12 Feb 2014 22:06:38 -0500
Subject: [PATCH] pg_upgrade: document use of file system and COW snapshots

---
 doc/src/sgml/pgupgrade.sgml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 3d529b29c1..bb3b6a0a93 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -569,7 +569,10 @@ psql --username postgres --file script.sql postgres
    the old server and run <command>rsync</> again to update the copy with any
    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">.
+   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.
   </para>
 
  <refsect2>
-- 
2.40.0