doc: clarify behavior of pg_upgrade's clone mode

Be more precise about the benefits of using clone mode.
This commit is contained in:
Bruce Momjian 2019-05-01 09:09:28 -04:00
parent 659e53498c
commit 26950273dc
1 changed files with 5 additions and 5 deletions

View File

@ -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>