aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2019-05-01 09:09:28 -0400
committerBruce Momjian <bruce@momjian.us>2019-05-01 09:09:28 -0400
commit26950273dc27ec7775029cffe1140165f942325d (patch)
treeb162bf667366d5eae1b0e7832f584e261a52e8dd /doc/src
parent659e53498c3c04e4f400323c02bef98fe8d13ec8 (diff)
downloadpostgresql-26950273dc27ec7775029cffe1140165f942325d.tar.gz
postgresql-26950273dc27ec7775029cffe1140165f942325d.zip
doc: clarify behavior of pg_upgrade's clone mode
Be more precise about the benefits of using clone mode.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/ref/pgupgrade.sgml10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 0c4b16d32ce..26e3f9ea2b9 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -382,11 +382,11 @@ NET STOP postgresql-&majorversion;
requires that the old and new cluster data directories be in the
same file system. (Tablespaces and <filename>pg_wal</filename> can be on
different file systems.)
- The clone mode provides the same speed and disk space advantages but will
- not leave the old cluster unusable after the upgrade. The clone mode
- also requires that the old and new data directories be in the same file
- system. The clone mode is only available on certain operating systems
- and file systems.
+ Clone mode provides the same speed and disk space advantages but
+ does not cause the old cluster to be unusable once the new cluster
+ is started. Clone mode also requires that the old and new data
+ directories be in the same file system. This mode is only available
+ on certain operating systems and file systems.
</para>
<para>