MIME-Version: 1.0
References: <CAHr8x_uxG6vjYaXGx_hCSKe5PQQ3FiZ8UUd822=YgkRwxQB8Nw@mail.gmail.com>
In-Reply-To: <CAHr8x_uxG6vjYaXGx_hCSKe5PQQ3FiZ8UUd822=YgkRwxQB8Nw@mail.gmail.com>
From: Olivier Gautherot <ogautherot@gautherot.net>
Date: Sun, 3 May 2026 15:18:47 +0200
Message-ID: <CAJ7S9TUOMU+2=_LnY7Rkd6764KM8d-3YrwABcfHm-QbuoqnyQg@mail.gmail.com>
Subject: Re: Tablespace size in TB
To: masheed ullah <masheedullah@gmail.com>
Cc: PostgreSQL General <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000001e948e0650e9a8bc"
Archived-At: <https://www.postgresql.org/message-id/CAJ7S9TUOMU%2B2%3D_LnY7Rkd6764KM8d-3YrwABcfHm-QbuoqnyQg%40mail.gmail.com>
Precedence: bulk

--0000000000001e948e0650e9a8bc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Masheed,

El dom, 3 de may de 2026, 11:36=E2=80=AFa.m., masheed ullah <masheedullah@g=
mail.com>
escribi=C3=B3:

> Hi,
>
> Postgres =3D Version 13
>
> OS=3DLinux 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*
>
>
>

--0000000000001e948e0650e9a8bc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>Hi Masheed,</div><div dir=3D"auto"><br><div class=3D=
"gmail_quote gmail_quote_container" dir=3D"auto"><div dir=3D"ltr" class=3D"=
gmail_attr">El dom, 3 de may de 2026, 11:36=E2=80=AFa.m., masheed ullah &lt=
;<a href=3D"mailto:masheedullah@gmail.com">masheedullah@gmail.com</a>&gt; e=
scribi=C3=B3:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div=
>Hi,</div><div><br></div><div><p style=3D"margin:0px 0px 1.1em;padding:0px;=
border:0px;font-variant-numeric:inherit;font-variant-east-asian:inherit;fon=
t-variant-alternates:inherit;font-stretch:inherit;line-height:inherit;font-=
family:-apple-system,BlinkMacSystemFont,&quot;Segoe UI Adjusted&quot;,&quot=
;Segoe UI&quot;,&quot;Liberation Sans&quot;,sans-serif;font-size-adjust:inh=
erit;font-kerning:inherit;font-feature-settings:inherit;font-size:15px;vert=
ical-align:baseline;box-sizing:inherit;clear:both;color:rgb(12,13,14)">Post=
gres =3D Version 13</p><p style=3D"margin:0px 0px 1.1em;padding:0px;border:=
0px;font-variant-numeric:inherit;font-variant-east-asian:inherit;font-varia=
nt-alternates:inherit;font-stretch:inherit;line-height:inherit;font-family:=
-apple-system,BlinkMacSystemFont,&quot;Segoe UI Adjusted&quot;,&quot;Segoe =
UI&quot;,&quot;Liberation Sans&quot;,sans-serif;font-size-adjust:inherit;fo=
nt-kerning:inherit;font-feature-settings:inherit;font-size:15px;vertical-al=
ign:baseline;box-sizing:inherit;clear:both;color:rgb(12,13,14)">OS=3DLinux =
Redhat version 8</p><p style=3D"margin:0px 0px 1.1em;padding:0px;border:0px=
;font-variant-numeric:inherit;font-variant-east-asian:inherit;font-variant-=
alternates:inherit;font-stretch:inherit;line-height:inherit;font-family:-ap=
ple-system,BlinkMacSystemFont,&quot;Segoe UI Adjusted&quot;,&quot;Segoe UI&=
quot;,&quot;Liberation Sans&quot;,sans-serif;font-size-adjust:inherit;font-=
kerning:inherit;font-feature-settings:inherit;font-size:15px;vertical-align=
:baseline;box-sizing:inherit;clear:both;color:rgb(12,13,14)">Our team is us=
ing 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 dat=
a in multiple tablespaces. It will not only improve the performance &amp; r=
educe the backup time.</p><p style=3D"margin:0px;padding:0px;border:0px;fon=
t-variant-numeric:inherit;font-variant-east-asian:inherit;font-variant-alte=
rnates:inherit;font-stretch:inherit;line-height:inherit;font-family:-apple-=
system,BlinkMacSystemFont,&quot;Segoe UI Adjusted&quot;,&quot;Segoe UI&quot=
;,&quot;Liberation Sans&quot;,sans-serif;font-size-adjust:inherit;font-kern=
ing:inherit;font-feature-settings:inherit;font-size:15px;vertical-align:bas=
eline;box-sizing:inherit;clear:both;color:rgb(12,13,14)">But I did not find=
 any Postgres best practice or blog, to show as a reference.</p></div></div=
></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">By =
any chance, do you mean partitions instead of tablespaces? Partitions are i=
ndeed recommended when your tables reach prohibitive sizes. With the releva=
nt partition key and indexes, it can significantly improve the performance =
and, with a smart backup strategy, reduce the backup size and time.</div><d=
iv dir=3D"auto"><br></div><div dir=3D"auto"><div dir=3D"ltr">Hope it helps<=
br>--</div><div dir=3D"ltr">Olivier Gautherot</div><div dir=3D"ltr"><br></d=
iv></div><div dir=3D"auto"><div class=3D"gmail_quote gmail_quote_container"=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_s=
ignature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><font fa=
ce=3D"sans-serif" size=3D"2">Best Regards,</font><font size=3D"3"> </font><=
font face=3D"sans-serif" size=3D"2"><br>
<b>Masheed <font size=3D"2">Ullah</font></b> <br>
</font><br></div><br></div></div></div>
</blockquote></div></div></div>

--0000000000001e948e0650e9a8bc--