Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wJceg-0004jF-05 for pgsql-general@arkaria.postgresql.org; Sun, 03 May 2026 19:39:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wJcee-004MYI-2C for pgsql-general@arkaria.postgresql.org; Sun, 03 May 2026 19:39:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wJcee-004MY8-14 for pgsql-general@lists.postgresql.org; Sun, 03 May 2026 19:39:04 +0000 Received: from sm-r-018-dus.org-dns.com ([89.107.70.8]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wJceb-00000000K95-49aS for pgsql-general@lists.postgresql.org; Sun, 03 May 2026 19:39:03 +0000 Received: from smarthost-dus.org-dns.com (localhost [127.0.0.1]) by smarthost-dus.org-dns.com (Postfix) with ESMTP id B5C53A232D for ; Sun, 3 May 2026 21:39:00 +0200 (CEST) X-Spam-Status: No, score=0.9 required=5.0 tests=AWL,BAYES_50,DKIM_INVALID, DKIM_SIGNED,DMARC_NONE,HTML_MESSAGE,KAM_INFOUSMEBIZ, MIME_HEADER_CTYPE_ONLY,SPF_HELO_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Tests: AWL=-1.024,BAYES_50=0.8,DKIM_INVALID=0.1,DKIM_SIGNED=0.1, DMARC_NONE=0.1,HTML_MESSAGE=0.001,KAM_INFOUSMEBIZ=0.75, MIME_HEADER_CTYPE_ONLY=0.1,SPF_HELO_PASS=-0.001 Received: from ha01s018.org-dns.com (ha01s018.org-dns.com [62.108.32.138]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smarthost-dus.org-dns.com (Postfix) with ESMTPS id 3D4F7A2036 for ; Sun, 3 May 2026 21:39:00 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gelassene-pferde.biz; s=default; t=1777837141; bh=YWgN6u8ZgwxgwhlrwJXuehQvfNPLBNUVjj9Eh31SKgM=; h=From:To:Subject; b=lRmUB1fgEldUKuAgsfdaxu1WK8d04ATXFFHaWF8B+R2moANHd5BkZQI2XiwmZz7ju 4Hhipnxrg2wNyOkBziUmRMYFE7Bjl+vHqa/t9UtOjsqlDlvAvFbS0sRvWJuxi8f6o7 WECMgFAymkN0m3JI8XrLB36ElgkOInr3A7+0qTv0= Authentication-Results: ha01s018.org-dns.com; spf=pass (sender IP is 146.185.68.202) smtp.mailfrom=thiemo@gelassene-pferde.biz smtp.helo=dummy.faircode.eu Received-SPF: pass (ha01s018.org-dns.com: connection is authenticated) Date: Sun, 3 May 2026 21:38:59 +0200 From: Thiemo Kellner To: pgsql-general Message-ID: In-Reply-To: References: Subject: Re: Tablespace size in TB Content-Type: multipart/alternative; boundary="----=_Part_2_44620553.1777837139679" X-Correlation-ID: X-PPP-Message-ID: <177783714164.3459392.8096829305517290421@ha01s018.org-dns.com> X-PPP-Vhost: gelassene-pferde.biz X-Virus-Scanned: clamav-milter 1.4.3 at smarthost-dus X-Virus-Status: Clean List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ------=_Part_2_44620553.1777837139679 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Even with Oracle you need to know the architecture of your storage to decid= e whether you can expect performance improvements. If you happen to have so= me kind of NAS, you partitions for the different table spaces might reside = on the very same hardware and you probably gain naught. 03.05.2026 14:27:01 masheed ullah : > Just to check like Oracle, parallelism=C2=A0works well with multiple tabl= espaces. > Moving tables/ indexes to multiple tablespaces to use the parallelism to = boost the backup speed. With a single tablespace, parallelism will not work= . >=20 > On Sun, May 3, 2026 at 3:21=E2=80=AFPM Laurenz Albe 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. >>=20 >> I am confused.=C2=A0 Yes, if you have more than a single (default) table= space, >> moving tables between tablespaces becomes possible and hence easier. >> But why would you want to move tables between tablespaces in the first p= lace? >>=20 >> Yours, >> Laurenz Albe >=20 >=20 >=20 ------=_Part_2_44620553.1777837139679 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Even with Orac= le you need to know the architecture of your storage to decide whether you = can expect performance improvements. If you happen to have some kind of NAS= , you partitions for the different table spaces might reside on the very sa= me hardware and you probably gain naught.

03.05.2026 14:27:01 masheed ullah <masheedullah@gmail.com>:

Just to check like Oracle, parallelism works well with multiple = tablespaces.=20
Moving tables/ indexes to multiple tablespaces to use the parallelis= m 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:=20
On Sun, 2026-05-03 at 14:10 +0200, Jan Karremans wrote:=20
> Contrary to Oracle, a table space in PostgreSQL is a directory= . And not a logical abstraction.=20
> Moving tables from one table space to another becomes so much = easier by that.=20

I am confused.  Yes, if you have more than a single (default) = tablespace,=20
moving tables between tablespaces becomes possible and hence easier= .=20
But why would you want to move tables between tablespaces in the fi= rst place?=20

Yours,=20
Laurenz Albe=20



------=_Part_2_44620553.1777837139679--