Horton

doc: expand note about pg_upgrade's --jobs option

Nathan Bossart <nathandbossart@gmail.com>

View thread
From: Nathan Bossart <nathandbossart@gmail.com>
To: pgsql-hackers@postgresql.org
Cc: magnus@hagander.net
Date: 2025-03-04T18:08:31Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

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

  2. Introduce framework for parallelizing various pg_upgrade tasks.

Attachments

Magnus noted to me off-list that the "et cetera" in the following sentence
in pg_upgrade's docs is doing quite a bit of heavy lifting:

	The --jobs 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.

I added the "et cetera" in commit 40e2e5e92b to cover the many follow-up
commits that parallelized various pg_upgrade tasks.  I was initially
worried that trying to list all the parallelized stuff would be too
verbose, but looking again, I think all the changes can be grouped into
"gathering cluster information" and "performing cluster checks."  The
attached patch replaces the "et cetera" with those two general categories.

-- 
nathan