public inbox for [email protected]
help / color / mirror / Atom feedRe: Tablespace size in TB
3+ messages / 2 participants
[nested] [flat]
* Re: Tablespace size in TB
@ 2026-05-03 12:21 Laurenz Albe <[email protected]>
2026-05-03 12:25 ` Re: Tablespace size in TB Jan Karremans <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Laurenz Albe @ 2026-05-03 12:21 UTC (permalink / raw)
To: Jan Karremans <[email protected]>; masheed ullah <[email protected]>; +Cc: Thiemo Kellner <[email protected]>; [email protected]
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Tablespace size in TB
2026-05-03 12:21 Re: Tablespace size in TB Laurenz Albe <[email protected]>
@ 2026-05-03 12:25 ` Jan Karremans <[email protected]>
2026-05-03 16:59 ` Re: Tablespace size in TB Laurenz Albe <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Jan Karremans @ 2026-05-03 12:25 UTC (permalink / raw)
To: Laurenz Albe <[email protected]>; +Cc: masheed ullah <[email protected]>; Thiemo Kellner <[email protected]>; [email protected]
My thinking would be to have the different directories on different tiers of storage.
Cheers,
Jan
> 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?
>
> Yours,
> Laurenz Albe
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Tablespace size in TB
2026-05-03 12:21 Re: Tablespace size in TB Laurenz Albe <[email protected]>
2026-05-03 12:25 ` Re: Tablespace size in TB Jan Karremans <[email protected]>
@ 2026-05-03 16:59 ` Laurenz Albe <[email protected]>
0 siblings, 0 replies; 3+ messages in thread
From: Laurenz Albe @ 2026-05-03 16:59 UTC (permalink / raw)
To: Jan Karremans <[email protected]>; +Cc: masheed ullah <[email protected]>; Thiemo Kellner <[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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2026-05-03 16:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-05-03 12:21 Re: Tablespace size in TB Laurenz Albe <[email protected]>
2026-05-03 12:25 ` Jan Karremans <[email protected]>
2026-05-03 16:59 ` Laurenz Albe <[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