| From: | masheed ullah <masheedullah(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Jan Karremans <karremans(dot)ja(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 12:26:45 |
| Message-ID: | CAHr8x_sCFOpufrmTPBF2nOFMyJfWG6EPHMfN+UOiKdfLF_kVdA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 PM 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?
>
> Yours,
> Laurenz Albe
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | masheed ullah | 2026-05-03 12:30:56 | Re: Tablespace size in TB |
| Previous Message | Jan Karremans | 2026-05-03 12:25:26 | Re: Tablespace size in TB |