We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 964c0d0 commit e2c84bcCopy full SHA for e2c84bc
doc/src/sgml/pgupgrade.sgml
@@ -372,7 +372,9 @@ pg_upgrade.exe
372
and then do the upgrade. You can use <command>pg_upgrade --check</>
373
to perform only the checks, even if the old server is still
374
running. <command>pg_upgrade --check</> will also outline any
375
- manual adjustments you will need to make after the upgrade.
+ manual adjustments you will need to make after the upgrade. If you
376
+ are going to be using link mode, you should use the <option>--link</>
377
+ option with <option>--check</option> to enable link-mode-specific checks.
378
<command>pg_upgrade</> requires write permission in the current directory.
379
</para>
380
0 commit comments