public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: masheed ullah <[email protected]>
Cc: Jan Karremans <[email protected]>
Cc: Thiemo Kellner <[email protected]>
Cc: [email protected]
Subject: Re: Tablespace size in TB
Date: Sun, 03 May 2026 19:04:29 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAHr8x_sCFOpufrmTPBF2nOFMyJfWG6EPHMfN+UOiKdfLF_kVdA@mail.gmail.com>
References: <CAHr8x_tgJh2vb8gyq-kmrbtKstaAYUpmWC3+umwGXhOZYeMxOQ@mail.gmail.com>
<[email protected]>
<[email protected]>
<CAHr8x_sCFOpufrmTPBF2nOFMyJfWG6EPHMfN+UOiKdfLF_kVdA@mail.gmail.com>
On Sun, 2026-05-03 at 15:26 +0300, masheed ullah wrote:
> Just to check like Oracle, parallelism works well with multiple tablespaces.
> Moving tables/ indexes to multiple tablespaces to use the parallelism to boost
> the backup speed. With a single tablespace, parallelism will not work.
That may be the case with Oracle, but not with PostgreSQL.
pg_basebackup will not parallelize at all.
I found the following article about backup tools useful:
https://thebuild.com/blog/2026/04/30/after-pgbackrest/
You should consider alternatives to parallelism, since parallelism
will only help up to the limit where the disk is saturated.
One think you should seriously consider is incremental backup,
which would reduce the backup time considerably (but not the
restore time).
Yours,
Laurenz Albe
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], [email protected], [email protected], [email protected]
Subject: Re: Tablespace size in TB
In-Reply-To: <[email protected]>
* 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