public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: Jan Karremans <[email protected]>
Cc: masheed ullah <[email protected]>
Cc: Thiemo Kellner <[email protected]>
Cc: [email protected]
Subject: Re: Tablespace size in TB
Date: Sun, 03 May 2026 18:59:41 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAHr8x_tgJh2vb8gyq-kmrbtKstaAYUpmWC3+umwGXhOZYeMxOQ@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
On Sun, 2026-05-03 at 14:25 +0200, Jan Karremans wrote:
>
> > On 3 May 2026, at 14:21, Laurenz Albe <[email protected]> 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?
>
> My thinking would be to have the different directories on different tiers of storage.
I see. That can indeed improve the throughput, but you don't need tablespaces for
that: it would be simpler to define a striped logical volume.
Yours,
Laurenz Albe
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Tablespace size in TB
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox