public inbox for [email protected]
help / color / mirror / Atom feedFrom: Olivier Gautherot <[email protected]>
To: masheed ullah <[email protected]>
Cc: PostgreSQL General <[email protected]>
Subject: Re: Tablespace size in TB
Date: Sun, 3 May 2026 15:18:47 +0200
Message-ID: <CAJ7S9TUOMU+2=_LnY7Rkd6764KM8d-3YrwABcfHm-QbuoqnyQg@mail.gmail.com> (raw)
In-Reply-To: <CAHr8x_uxG6vjYaXGx_hCSKe5PQQ3FiZ8UUd822=YgkRwxQB8Nw@mail.gmail.com>
References: <CAHr8x_uxG6vjYaXGx_hCSKe5PQQ3FiZ8UUd822=YgkRwxQB8Nw@mail.gmail.com>
Hi Masheed,
El dom, 3 de may de 2026, 11:36 a.m., masheed ullah <[email protected]>
escribió:
> 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.
>
By any chance, do you mean partitions instead of tablespaces? Partitions
are indeed recommended when your tables reach prohibitive sizes. With the
relevant partition key and indexes, it can significantly improve the
performance and, with a smart backup strategy, reduce the backup size and
time.
Hope it helps
--
Olivier Gautherot
> --
> Best Regards,
> *Masheed Ullah*
>
>
>
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: <CAJ7S9TUOMU+2=_LnY7Rkd6764KM8d-3YrwABcfHm-QbuoqnyQg@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