public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: pg_dump -j
Date: Wed, 12 Nov 2025 11:11:56 -0500
Message-ID: <CANzqJaCfOQBa06TfkAs63dbnLRegOtOdDumKdn2S101KkiFrVA@mail.gmail.com> (raw)
In-Reply-To: <CAN6TVjmRACGXcz3XoiOKw3ws1tBs_bnwa3AD==vyxmEdUJ=z_g@mail.gmail.com>
References: <CAN6TVjmRACGXcz3XoiOKw3ws1tBs_bnwa3AD==vyxmEdUJ=z_g@mail.gmail.com>
On Wed, Nov 12, 2025 at 10:34 AM Sam Stearns <[email protected]> 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!
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: pg_dump -j
In-Reply-To: <CANzqJaCfOQBa06TfkAs63dbnLRegOtOdDumKdn2S101KkiFrVA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox