| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_dump -j |
| Date: | 2025-11-12 16:11:56 |
| Message-ID: | CANzqJaCfOQBa06TfkAs63dbnLRegOtOdDumKdn2S101KkiFrVA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Nov 12, 2025 at 10:34 AM Sam Stearns <sam(dot)stearns(at)dat(dot)com> wrote:
> Howdy,
>
> Would someone be able to advise on the correct setting for the -j option
> of pg_dump to run the dump in parallel, please? Is it based on CPU count,
> or something else? The output of nproc is 32.
>
I'd certainly never go *beyond* $(nproc), but since COPY generates a lot of
IO and compression burns through CPU, it all depends on the system's other
workload. Only you know what your system's other workload is when pg_dump
is running.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sbob | 2025-11-12 18:09:36 | vacuum process running for more than 2 days, still in scanning heap phase |
| Previous Message | Peter Gram | 2025-11-12 15:43:21 | Re: Postgres HA Deployment Questions |