| From: | Olivier Gautherot <ogautherot(at)gautherot(dot)net> |
|---|---|
| To: | masheed ullah <masheedullah(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Tablespace size in TB |
| Date: | 2026-05-03 13:18:47 |
| Message-ID: | CAJ7S9TUOMU+2=_LnY7Rkd6764KM8d-3YrwABcfHm-QbuoqnyQg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Masheed,
El dom, 3 de may de 2026, 11:36 a.m., masheed ullah <masheedullah(at)gmail(dot)com>
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*
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2026-05-03 14:43:43 | Re: Tablespace size in TB |
| Previous Message | Jan Karremans | 2026-05-03 12:47:56 | Re: Tablespace size in TB |