From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 11 Apr 2017 16:14:01 +0000 (-0400)
Subject: doc: clearify pg_upgrade default copy behavior
X-Git-Tag: REL_10_BETA1~301
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1e298b8dbb3220a0d5e073e0ad6a8afd35042c2a;p=postgresql

doc: clearify pg_upgrade default copy behavior

Reported-by: Marek <marek.cvoren@gmail.com>

Discussion: 20170328110253.2695.62609@wrigleys.postgresql.org
---

diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 49aaf513f5..bf58a0a7d8 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -336,8 +336,8 @@ NET STOP postgresql-9.0
      Always run the <application>pg_upgrade</> binary of the new server, not the old one.
      <application>pg_upgrade</> requires the specification of the old and new cluster's
      data and executable (<filename>bin</>) directories. You can also specify
-     user and port values, and whether you want the data linked instead of
-     copied (the default).
+     user and port values, and whether you want the data files linked
+     instead of the default copy behavior.
     </para>
 
     <para>