MIME-Version: 1.0
References: <CAHr8x_tgJh2vb8gyq-kmrbtKstaAYUpmWC3+umwGXhOZYeMxOQ@mail.gmail.com>
 <CDB30DC3-C4C6-4437-93E8-6440E0B03782@gmail.com> <ba2496302b3d6ae301b90f442bd22dc63cd285af.camel@cybertec.at>
In-Reply-To: <ba2496302b3d6ae301b90f442bd22dc63cd285af.camel@cybertec.at>
From: masheed ullah <masheedullah@gmail.com>
Date: Sun, 3 May 2026 15:26:45 +0300
Message-ID: <CAHr8x_sCFOpufrmTPBF2nOFMyJfWG6EPHMfN+UOiKdfLF_kVdA@mail.gmail.com>
Subject: Re: Tablespace size in TB
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Jan Karremans <karremans.ja@gmail.com>, Thiemo Kellner <thiemo@gelassene-pferde.biz>, 
	pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000013cceb0650e8ee87"
Archived-At: <https://www.postgresql.org/message-id/CAHr8x_sCFOpufrmTPBF2nOFMyJfWG6EPHMfN%2BUOiKdfLF_kVdA%40mail.gmail.com>
Precedence: bulk

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

Just to check like Oracle, parallelism works well with multiple tablespaces=
.
Moving tables/ indexes to multiple tablespaces to use the parallelism to
boost the backup speed. With a single tablespace, parallelism will not work=
.

On Sun, May 3, 2026 at 3:21=E2=80=AFPM Laurenz Albe <laurenz.albe@cybertec.=
at>
wrote:

> On Sun, 2026-05-03 at 14:10 +0200, Jan Karremans wrote:
> > Contrary to Oracle, a table space in PostgreSQL is a directory. And not
> a logical abstraction.
> > Moving tables from one table space to another becomes so much easier by
> that.
>
> I am confused.  Yes, if you have more than a single (default) tablespace,
> moving tables between tablespaces becomes possible and hence easier.
> But why would you want to move tables between tablespaces in the first
> place?
>
> Yours,
> Laurenz Albe
>

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

<div dir=3D"ltr"><div dir=3D"ltr">Just to check like Oracle, parallelism=C2=
=A0works well with multiple tablespaces.<br>Moving tables/ indexes to multi=
ple tablespaces to use the parallelism to boost the backup speed. With a si=
ngle tablespace, parallelism will not work.</div><br><div class=3D"gmail_qu=
ote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Ma=
y 3, 2026 at 3:21=E2=80=AFPM Laurenz Albe &lt;<a href=3D"mailto:laurenz.alb=
e@cybertec.at">laurenz.albe@cybertec.at</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">On Sun, 2026-05-03 at 14:10 +0200, J=
an Karremans wrote:<br>
&gt; Contrary to Oracle, a table space in PostgreSQL is a directory. And no=
t a logical abstraction.<br>
&gt; Moving tables from one table space to another becomes so much easier b=
y that.<br>
<br>
I am confused.=C2=A0 Yes, if you have more than a single (default) tablespa=
ce,<br>
moving tables between tablespaces becomes possible and hence easier.<br>
But why would you want to move tables between tablespaces in the first plac=
e?<br>
<br>
Yours,<br>
Laurenz Albe<br>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><div dir=3D"=
ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div><br></div></div></div>=
</div>

--00000000000013cceb0650e8ee87--