Skip to content

Commit 2695027

Browse files
committed
doc: clarify behavior of pg_upgrade's clone mode
Be more precise about the benefits of using clone mode.
1 parent 659e534 commit 2695027

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

doc/src/sgml/ref/pgupgrade.sgml

+5-5
Original file line numberDiff line numberDiff line change
@@ -382,11 +382,11 @@ NET STOP postgresql-&majorversion;
382382
requires that the old and new cluster data directories be in the
383383
same file system. (Tablespaces and <filename>pg_wal</filename> can be on
384384
different file systems.)
385-
The clone mode provides the same speed and disk space advantages but will
386-
not leave the old cluster unusable after the upgrade. The clone mode
387-
also requires that the old and new data directories be in the same file
388-
system. The clone mode is only available on certain operating systems
389-
and file systems.
385+
Clone mode provides the same speed and disk space advantages but
386+
does not cause the old cluster to be unusable once the new cluster
387+
is started. Clone mode also requires that the old and new data
388+
directories be in the same file system. This mode is only available
389+
on certain operating systems and file systems.
390390
</para>
391391

392392
<para>

0 commit comments

Comments
 (0)