From 23c5a41c0b7a61433b1cd0e6315b9c4bbc536608 Mon Sep 17 00:00:00 2001 From: Nathan Bossart Date: Tue, 4 Mar 2025 11:52:45 -0600 Subject: [PATCH v1 1/1] doc: Expand note about pg_upgrade's --jobs option. Commit 40e2e5e92b and several follow-up commits parallelized many pg_upgrade tasks but did not add much detail to the documentation. This commit expands the existing note for --jobs to include the general categories of newly-parallelized tasks. Reported-by: Magnus Hagander Discussion: ??? --- doc/src/sgml/ref/pgupgrade.sgml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index 7bdd85c5cff..18c71355085 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -534,8 +534,9 @@ 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 + for copying/linking of files, dumping and restoring database schemas, + gathering cluster information, and performing cluster checks; + 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. -- 2.39.5 (Apple Git-154)