Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit2695027

Browse files
committed
doc: clarify behavior of pg_upgrade's clone mode
Be more precise about the benefits of using clone mode.
1 parent659e534 commit2695027

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

‎doc/src/sgml/ref/pgupgrade.sgml

Lines changed: 5 additions & 5 deletions
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 clonemode provides the same speed and disk space advantages but will
386-
notleave the old cluster unusableafter theupgrade. The clone mode
387-
also requires that the old and new data directories be in the same file
388-
system.The clonemode is only available on certain operating systems
389-
and file systems.
385+
Clonemode provides the same speed and disk space advantages but
386+
doesnotcause the old clusterto beunusableonce thenew cluster
387+
is started. Clone modealso requires that the old and new data
388+
directories be in the same filesystem.Thismode is only available
389+
on certain operating systemsand file systems.
390390
</para>
391391

392392
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp