From 26950273dc27ec7775029cffe1140165f942325d Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 1 May 2019 09:09:28 -0400 Subject: [PATCH] doc: clarify behavior of pg_upgrade's clone mode Be more precise about the benefits of using clone mode. --- doc/src/sgml/ref/pgupgrade.sgml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index 0c4b16d32c..26e3f9ea2b 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 pg_wal 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. -- 2.40.0