| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Jan Karremans <karremans(dot)ja(at)gmail(dot)com> |
| Cc: | masheed ullah <masheedullah(at)gmail(dot)com>, Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Tablespace size in TB |
| Date: | 2026-05-03 16:59:41 |
| Message-ID: | 16220683f58d6ce349aee3511d4a6328d03daa82.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 2026-05-03 at 14:25 +0200, Jan Karremans wrote:
>
> > On 3 May 2026, at 14:21, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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?
>
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2026-05-03 17:04:29 | Re: Tablespace size in TB |
| Previous Message | Greg Hennessy | 2026-05-03 15:54:57 | Re: Tablespace size in TB |