public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Tablespace size in TB
Date: Sun, 3 May 2026 10:43:43 -0400
Message-ID: <CANzqJaDEnVJjJ2tcyc_SShMwKN-TSSQisvqGQCkHRgEmzOCXqw@mail.gmail.com> (raw)
In-Reply-To: <CAHr8x_uxG6vjYaXGx_hCSKe5PQQ3FiZ8UUd822=YgkRwxQB8Nw@mail.gmail.com>
References: <CAHr8x_uxG6vjYaXGx_hCSKe5PQQ3FiZ8UUd822=YgkRwxQB8Nw@mail.gmail.com>
On Sun, May 3, 2026 at 5:36 AM masheed ullah <[email protected]> wrote:
> Hi,
>
> Postgres = Version 13
>
> OS=Linux Redhat version 8
>
> Our team is using a single tablespace for the whole database. Its size is
> more than 13TB. I am from an Oracle background and want to suggest that
> they split the data in multiple tablespaces. It will not only improve the
> performance & reduce the backup time.
>
> But I did not find any Postgres best practice or blog, to show as a
> reference.
>
To reinforce Jan's comment: a PG tablespace is *just a directory*. Nothing
more, nothing less.
If your 13TB database is on one single spindle (or even SSD/NVMe), then
yes, adding more spindles or SSDs would be useful. But if it's already on
multiple spindles, then LVM solves the problem for you.
As for long backup times, that's a function of hardware. How many threads
are you using? How parallel is the backup disk (or SAN)? How's the network
configured? Etc etc.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
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]
Subject: Re: Tablespace size in TB
In-Reply-To: <CANzqJaDEnVJjJ2tcyc_SShMwKN-TSSQisvqGQCkHRgEmzOCXqw@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