We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see ourdocumentation.
There was an error while loading.Please reload this page.
1 parentbcec58c commit3f735aeCopy full SHA for 3f735ae
doc/src/sgml/pgupgrade.sgml
@@ -570,9 +570,10 @@ psql --username postgres --file script.sql postgres
570
changes to make it consistent. You might want to exclude some
571
files, e.g. <filename>postmaster.pid</>, as documented in <xref
572
linkend="backup-lowlevel-base-backup">. If your file system supports
573
- file system snapshots or copy-on-write file copying, you can use that
574
- to make a backup of the old cluster, though the snapshot and copies
575
- 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
576
+ is down.
577
</para>
578
579
<refsect2>