| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: doc: expand note about pg_upgrade's --jobs option |
| Date: | 2025-03-05 12:52:40 |
| Message-ID: | CABUevEyGocYk1HtvULvjrW+qvS-64Yru6Emaj-CAO6hZ2HbEnw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 5, 2025 at 11:00 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > On 4 Mar 2025, at 19:08, Nathan Bossart <nathandbossart(at)gmail(dot)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)?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2025-03-05 12:53:04 | Re: support fast default for domain with constraints |
| Previous Message | Michael Paquier | 2025-03-05 12:28:23 | Re: Monitoring gaps in XLogWalRcvWrite() for the WAL receiver |