From 540c39cc56f51b27bff9a6fc78d6524564953c6c Mon Sep 17 00:00:00 2001 From: Michael Paquier Date: Sun, 11 Jan 2026 15:24:02 +0900 Subject: [PATCH] doc: Improve description of pg_restore --jobs The parameter name used for the option value was named "number-of-jobs", which was inconsistent with what all the other tools with an option called --jobs use. This commit updates the parameter name to "njobs". Author: Tatsuro Yamada Discussion: https://postgr.es/m/CAOKkKFvHqA6Tny0RKkezWVfVV91nPJyj4OGtMi3C1RznDVXqrg@mail.gmail.com --- doc/src/sgml/ref/pg_restore.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index a468a38361a..2c295bbf8dc 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -259,14 +259,14 @@ PostgreSQL documentation - - + + Run the most time-consuming steps of pg_restore — those that load data, create indexes, or create constraints — concurrently, using up - to number-of-jobs + to njobs concurrent sessions. This option can dramatically reduce the time to restore a large database to a server running on a multiprocessor machine. This option is ignored when emitting a script