public inbox for [email protected]  

help / color / mirror / Atom feed

From: Laurenz Albe <[email protected]>
To: masheed ullah <[email protected]>
To: [email protected]
Subject: Re: Tablespace size in TB
Date: Sun, 03 May 2026 14:18:01 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAHr8x_uxG6vjYaXGx_hCSKe5PQQ3FiZ8UUd822=YgkRwxQB8Nw@mail.gmail.com>
References: <CAHr8x_uxG6vjYaXGx_hCSKe5PQQ3FiZ8UUd822=YgkRwxQB8Nw@mail.gmail.com>

On Sun, 2026-05-03 at 12:35 +0300, masheed ullah wrote:
> 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.

Normally, using tablespaces won't speed up processing or backup; it just makes
administration slightly more complicated.
You shouldn't have created a tablespace in the first place (the default tablespace
is good), and I don't think you'll benefit from having more tablespaces.

To be more precise, a correct answer would depend on your backup method.
If you are using storage techniques to copy the 13TB, and those storage
techniques become faster if you have more than a single file system,
then you could benefit from more tabespaces.  Otherwise you won't.

What makes sense to split up is large tables.  Using partitioning might
make the individual partitions easier to maintain.

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]
  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