doc: Adjust some notes about pg_upgrade's file transfer modes.

--copy-file-range and --swap were not mentioned in a few places
that discuss the available file transfer modes.  This entire page
would likely benefit from an overhaul, but that's v19 material at
this point.

Oversights in commits d93627bcbe and 626d7236b6.

diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index da26161904387d33c8c94fb6bd450b5ea4d4a172..df13365b287dc309fc4ccaf42f22196c61e03221 100644 (file)
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -540,7 +540,7 @@ NET STOP postgresql-&majorversion;
      Always run the pg_upgrade binary of the new server, not the old one.
      pg_upgrade requires the specification of the old and new cluster's
      data and executable (bin) directories. You can also specify
-     user and port values, and whether you want the data files linked or cloned
+     user and port values, and whether you want the data files linked, cloned, or swapped
      instead of the default copy behavior.
     
 
@@ -589,8 +589,9 @@ pg_upgrade.exe
      to perform only the checks, even if the old server is still
      running. pg_upgrade --check will also outline any
      manual adjustments you will need to make after the upgrade.  If you
-     are going to be using link or clone mode, you should use the option
-     --link or --clone with
+     are going to be using link, clone, copy-file-range, or swap mode, you
+     should use the option --link, --clone,
+     --copy-file-range, or --swap with
      --check to enable mode-specific checks.
      pg_upgrade requires write permission in the current directory.
     
@@ -880,7 +881,7 @@ psql --username=postgres --file=script.sql postgres
 
       
        
-        If the --link option was not
+        If neither --link nor --swap was
         used, the old cluster was unmodified;  it can be restarted.