diff options
author | Bruce Momjian | 2017-04-11 16:14:01 +0000 |
---|---|---|
committer | Bruce Momjian | 2017-04-11 16:14:09 +0000 |
commit | 1e298b8dbb3220a0d5e073e0ad6a8afd35042c2a (patch) | |
tree | c2a663e5795211bfa0e806bd024c07795dd5c5e5 | |
parent | 4c3b59abf4c476843bca23de7fb66d647627f30e (diff) |
doc: clearify pg_upgrade default copy behavior
Reported-by: Marek <[email protected]>
Discussion: [email protected]
-rw-r--r-- | doc/src/sgml/ref/pgupgrade.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
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> |