doc: clarify behavior of pg_upgrade's clone mode
Be more precise about the benefits of using clone mode.
This commit is contained in:
parent
659e53498c
commit
26950273dc
|
@ -382,11 +382,11 @@ NET STOP postgresql-&majorversion;
|
||||||
requires that the old and new cluster data directories be in the
|
requires that the old and new cluster data directories be in the
|
||||||
same file system. (Tablespaces and <filename>pg_wal</filename> can be on
|
same file system. (Tablespaces and <filename>pg_wal</filename> can be on
|
||||||
different file systems.)
|
different file systems.)
|
||||||
The clone mode provides the same speed and disk space advantages but will
|
Clone mode provides the same speed and disk space advantages but
|
||||||
not leave the old cluster unusable after the upgrade. The clone mode
|
does not cause the old cluster to be unusable once the new cluster
|
||||||
also requires that the old and new data directories be in the same file
|
is started. Clone mode also requires that the old and new data
|
||||||
system. The clone mode is only available on certain operating systems
|
directories be in the same file system. This mode is only available
|
||||||
and file systems.
|
on certain operating systems and file systems.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
|
Loading…
Reference in New Issue