database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-31 22:04:40 +03:00
Code Activity

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

Browse Source 
--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.
This commit is contained in:
Nathan Bossart
2025-04-01 14:37:47 -05:00
parent 00066aa173
commit 5aec7e07fb
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/ref/pgupgrade.sgml
View File

@ -540,7 +540,7 @@ NET STOP postgresql-&majorversion;
Always run the <application>pg_upgrade</application> binary of the new server, not the old one. Always run the <application>pg_upgrade</application> binary of the new server, not the old one.
<application>pg_upgrade</application> requires the specification of the old and new cluster's <application>pg_upgrade</application> requires the specification of the old and new cluster's
data and executable (<filename>bin</filename>) directories. You can also specify data and executable (<filename>bin</filename>) 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. instead of the default copy behavior.
</para> </para>
@ -589,8 +589,9 @@ pg_upgrade.exe
to perform only the checks, even if the old server is still to perform only the checks, even if the old server is still
running. <command>pg_upgrade --check</command> will also outline any running. <command>pg_upgrade --check</command> will also outline any
manual adjustments you will need to make after the upgrade. If you 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 are going to be using link, clone, copy-file-range, or swap mode, you
<option>--link</option> or <option>--clone</option> with should use the option <option>--link</option>, <option>--clone</option>,
<option>--copy-file-range</option>, or <option>--swap</option> with
<option>--check</option> to enable mode-specific checks. <option>--check</option> to enable mode-specific checks.
<command>pg_upgrade</command> requires write permission in the current directory. <command>pg_upgrade</command> requires write permission in the current directory.
</para> </para>
@ -880,7 +881,7 @@ psql --username=postgres --file=script.sql postgres
<listitem> <listitem>
<para> <para>
If the <option>--link</option> option was <emphasis>not</emphasis> If neither <option>--link</option> nor <option>--swap</option> was
used, the old cluster was unmodified; it can be restarted. used, the old cluster was unmodified; it can be restarted.
</para> </para>
</listitem> </listitem>