Re: Tablespace size in TB

On Sun, May 3, 2026 at 5:36 AM masheed ullah <masheedullah(at)gmail(dot)com> 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!