public inbox for [email protected]
help / color / mirror / Atom feedTablespace size in TB
7+ messages / 5 participants
[nested] [flat]
* Tablespace size in TB
@ 2026-05-03 09:35 masheed ullah <[email protected]>
2026-05-03 10:23 ` Tablespace size in TB Thiemo Kellner <[email protected]>
2026-05-03 10:28 ` Tablespace size in TB Thiemo Kellner <[email protected]>
2026-05-03 12:18 ` Re: Tablespace size in TB Laurenz Albe <[email protected]>
2026-05-03 14:43 ` Re: Tablespace size in TB Ron Johnson <[email protected]>
0 siblings, 4 replies; 7+ messages in thread
From: masheed ullah @ 2026-05-03 09:35 UTC (permalink / raw)
To: [email protected]
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.
--
Best Regards,
*Masheed Ullah*
^ permalink raw reply [nested|flat] 7+ messages in thread
* Tablespace size in TB
2026-05-03 09:35 Tablespace size in TB masheed ullah <[email protected]>
@ 2026-05-03 10:23 ` Thiemo Kellner <[email protected]>
3 siblings, 0 replies; 7+ messages in thread
From: Thiemo Kellner @ 2026-05-03 10:23 UTC (permalink / raw)
To: [email protected]
Hi
Is there a reason, you employ a version of PostgreSQL and OS too, that is no longer supported? Did you check, that v13 supports that kind of table spaces already? Maybe this support has been added only in a more recent version.
Kind regards
Thiemo
^ permalink raw reply [nested|flat] 7+ messages in thread
* Tablespace size in TB
2026-05-03 09:35 Tablespace size in TB masheed ullah <[email protected]>
@ 2026-05-03 10:28 ` Thiemo Kellner <[email protected]>
2026-05-03 10:45 ` Re: Tablespace size in TB masheed ullah <[email protected]>
3 siblings, 1 reply; 7+ messages in thread
From: Thiemo Kellner @ 2026-05-03 10:28 UTC (permalink / raw)
To: [email protected]
Maybe you are looking for https://www.postgresql.org/docs/13/manage-ag-tablespaces.html
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Tablespace size in TB
2026-05-03 09:35 Tablespace size in TB masheed ullah <[email protected]>
2026-05-03 10:28 ` Tablespace size in TB Thiemo Kellner <[email protected]>
@ 2026-05-03 10:45 ` masheed ullah <[email protected]>
2026-05-03 12:10 ` Re: Tablespace size in TB Jan Karremans <[email protected]>
0 siblings, 1 reply; 7+ messages in thread
From: masheed ullah @ 2026-05-03 10:45 UTC (permalink / raw)
To: Thiemo Kellner <[email protected]>; +Cc: [email protected]
Thank you Thiemo, yes the version 13 is outdated. Team is planning for an
upgrade.
I don't find any recommendations for splitting the single tablespace to
multiple.
So I need best practices / recommendations for Postgres.
On Sun, May 3, 2026 at 1:28 PM Thiemo Kellner <[email protected]>
wrote:
> Maybe you are looking for
> https://www.postgresql.org/docs/13/manage-ag-tablespaces.html
>
Best Regards,
*Khattak*
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Tablespace size in TB
2026-05-03 09:35 Tablespace size in TB masheed ullah <[email protected]>
2026-05-03 10:28 ` Tablespace size in TB Thiemo Kellner <[email protected]>
2026-05-03 10:45 ` Re: Tablespace size in TB masheed ullah <[email protected]>
@ 2026-05-03 12:10 ` Jan Karremans <[email protected]>
0 siblings, 0 replies; 7+ messages in thread
From: Jan Karremans @ 2026-05-03 12:10 UTC (permalink / raw)
To: masheed ullah <[email protected]>; +Cc: Thiemo Kellner <[email protected]>; [email protected]
--Apple-Mail-03581CAA-3D6F-4DE1-BB93-67499FD4E8D0
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html class=3D"apple-mail-supports-explicit-dark-mode"><head><meta http-equi=
v=3D"content-type" content=3D"text/html; charset=3Dutf-8"></head><body dir=3D=
"auto">Hi Masheed,<div><br></div><div>Contrary to Oracle, a table space in P=
ostgreSQL is a directory. And not a logical abstraction.</div><div>Moving ta=
bles from one table space to another becomes so much easier by that.</div><d=
iv><br></div><div>Does that help?</div><div><br></div><div>Cheers,</div><div=
>Jan</div><div><br id=3D"lineBreakAtBeginningOfSignature"><div dir=3D"ltr">V=
erstuurd vanaf mijn iPhone</div><div dir=3D"ltr"><br><blockquote type=3D"cit=
e">Op 3 mei 2026 om 12:45 heeft masheed ullah <[email protected]>=
het volgende geschreven:<br><br></blockquote></div><blockquote type=3D"cite=
"><div dir=3D"ltr">=EF=BB=BF<div dir=3D"ltr"><div dir=3D"ltr">Thank you Thie=
mo, yes the version 13 is outdated. Team is planning for an upgrade.&n=
bsp;<div>I don't find any recommendations for splitting the single=
tablespace to multiple.</div><div>So I need best practices / recommendation=
s for Postgres.</div></div><br><div class=3D"gmail_quote gmail_quote_co=
ntainer"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, May 3, 2026 at 1:28=E2=
=80=AFPM Thiemo Kellner <<a href=3D"mailto:[email protected]">t=
[email protected]</a>> wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">
=20
=20
=20
<div>
<span dir=3D"ltr" style=3D"margin-top:0px;margin-bottom:0px">Maybe you are=
looking for <a href=3D"https://www.postgresql.org/docs/13/manage-ag-tablesp=
aces.html" target=3D"_blank">https://www.postgresql.org/docs/13/manage-ag-ta=
blespaces.html</a></span>
<br>
</div>
</blockquote></div><div><br></div><div dir=3D"ltr" class=3D"gmail_signature"=
><div dir=3D"ltr"><div><font face=3D"sans-serif" size=3D"2">Best Regards,</f=
ont><font size=3D"3"> </font><font face=3D"sans-serif" size=3D"2"><br><b>Kha=
ttak</b><br>
</font><br></div><br></div></div></div>
</div></blockquote></div></body></html>=
--Apple-Mail-03581CAA-3D6F-4DE1-BB93-67499FD4E8D0--
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Tablespace size in TB
2026-05-03 09:35 Tablespace size in TB masheed ullah <[email protected]>
@ 2026-05-03 12:18 ` Laurenz Albe <[email protected]>
3 siblings, 0 replies; 7+ messages in thread
From: Laurenz Albe @ 2026-05-03 12:18 UTC (permalink / raw)
To: masheed ullah <[email protected]>; [email protected]
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
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Tablespace size in TB
2026-05-03 09:35 Tablespace size in TB masheed ullah <[email protected]>
@ 2026-05-03 14:43 ` Ron Johnson <[email protected]>
3 siblings, 0 replies; 7+ messages in thread
From: Ron Johnson @ 2026-05-03 14:43 UTC (permalink / raw)
To: pgsql-general
On Sun, May 3, 2026 at 5:36 AM masheed ullah <[email protected]> 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!
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2026-05-03 14:43 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-05-03 09:35 Tablespace size in TB masheed ullah <[email protected]>
2026-05-03 10:23 ` Thiemo Kellner <[email protected]>
2026-05-03 10:28 ` Thiemo Kellner <[email protected]>
2026-05-03 10:45 ` masheed ullah <[email protected]>
2026-05-03 12:10 ` Jan Karremans <[email protected]>
2026-05-03 12:18 ` Laurenz Albe <[email protected]>
2026-05-03 14:43 ` Ron Johnson <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox