From e7f8633672530fb06dac72271cda429ad873a640 Mon Sep 17 00:00:00 2001 From: Nathan Bossart Date: Wed, 5 Mar 2025 10:19:27 -0600 Subject: [PATCH v2 1/1] doc: Adjust note about pg_upgrade's --jobs option. Reported-by: Magnus Hagander Reviewed-by: ??? Discussion: https://postgr.es/m/Z8dBn_5iGLNuYiPo%40nathan --- doc/src/sgml/ref/pgupgrade.sgml | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index 6ca20f19ec2..10911d81174 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -565,12 +565,11 @@ NET STOP postgresql-&majorversion; - The 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 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. -- 2.39.5 (Apple Git-154)