diff options
| author | Bruce Momjian <bruce@momjian.us> | 2014-02-12 22:06:38 -0500 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2014-02-12 22:07:03 -0500 |
| commit | bcec58cf1ebf20ea237be042d3ef774f887557a9 (patch) | |
| tree | 1e9e609c346c5814271020f31200502b940dd512 /doc/src | |
| parent | 4a6f136c4676bd183b5c1145387eedd837c56ffa (diff) | |
| download | postgresql-bcec58cf1ebf20ea237be042d3ef774f887557a9.tar.gz postgresql-bcec58cf1ebf20ea237be042d3ef774f887557a9.zip | |
pg_upgrade: document use of file system and COW snapshots
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/pgupgrade.sgml | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index 3d529b29c12..bb3b6a0a933 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> |