database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-09 17:03:00 +03:00
Code Activity

doc: Adjust note about pg_upgrade's --jobs option.

Browse Source 
Presently, this section lists a couple of parallelized parts of
pg_upgrade and suggests a starting point for setting the --jobs
option.  The list of parallelized tasks is not particularly
actionable, and the phrasing for the --jobs recommendation is
confusing to some readers.

This commit attempts to improve this section by eliminating the
list of parallelized tasks and instead highlighting that --jobs is
most useful for clusters with multiple databases or tablespaces.
Additionally, the recommendation for setting --jobs is simplified
to suggest starting with the number of CPU cores.

Reported-by: Magnus Hagander <magnus@hagander.net>
Reviewed-by: Daniel Gustafsson <daniel@yesql.se>
Reviewed-by: Magnus Hagander <magnus@hagander.net>
Discussion: https://postgr.es/m/Z8dBn_5iGLNuYiPo%40nathan
This commit is contained in:
Nathan Bossart
2025-03-08 14:28:16 -06:00
parent 1852aea3f5
commit 3c472a1829
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -533,12 +533,11 @@ NET STOP postgresql-&majorversion;
</para>
<para>
The <option>--jobs</option> option allows multiple CPU cores to be used
for copying/linking of files, dumping and restoring database schemas
in parallel, etc.; a good place to start is the maximum of the number of
CPU cores and tablespaces. This option can dramatically reduce the
time to upgrade a multi-database server running on a multiprocessor
machine.
Setting <option>--jobs</option> to 2 or higher allows pg_upgrade to
process multiple databases and tablespaces in parallel. A good starting
point is the number of CPU cores on the machine. This option can
substantially reduce the upgrade time for multi-database and
multi-tablespace servers.
</para>
<para>