Re: doc: expand note about pg_upgrade's --jobs option - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: doc: expand note about pg_upgrade's --jobs option
Date
Msg-id CABUevEyGocYk1HtvULvjrW+qvS-64Yru6Emaj-CAO6hZ2HbEnw@mail.gmail.com
Whole thread Raw
In response to Re: doc: expand note about pg_upgrade's --jobs option  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: doc: expand note about pg_upgrade's --jobs option
List pgsql-hackers
On Wed, Mar 5, 2025 at 11:00 AM Daniel Gustafsson <daniel@yesql.se> wrote:
> On 4 Mar 2025, at 19:08, Nathan Bossart <nathandbossart@gmail.com> wrote:

> The attached patch replaces the "et cetera" with those two general categories.

LGTM.

Another option that I think would also work is to just cut down the details to just "The <option>--jobs</option> option allows multiple CPU cores to be used".

I think this is also slightly confusing, but maybe that's a non-native-english thing: "a good place to start is the maximum of the number of  CPU cores and tablespaces.". Am I supposed to set it to max(cpucores, ntablespaces) or to max(cpucores+ntablespaces)?

--

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Monitoring gaps in XLogWalRcvWrite() for the WAL receiver
Next
From: jian he
Date:
Subject: Re: support fast default for domain with constraints