| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Thomas Flatley <FLATLEYT(at)outlook(dot)com> |
| Cc: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Max# of tablespaces |
| Date: | 2021-01-05 22:01:59 |
| Message-ID: | D12A2423-2168-4B09-BDD7-9D8B73D02065@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Jan 5, 2021, at 13:55, Thomas Flatley <FLATLEYT(at)outlook(dot)com> wrote:
>
> As far as I can tell, each tablespace is a partition, and I assume they felt this was the best way to perform partition maintenance - again, I don’t know ,
It's a very common Oracle-ism to have a lot of tablespaces, in part because (IIRC) Oracle makes it an incredible pain in the neck to add tablespaces once the DB is in use. For sharding purposes, you probably want schemas in PostgreSQL instead of tablespaces, although having that many schemas is going to not be optimal, either.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2021-01-05 22:02:12 | Re: Max# of tablespaces |
| Previous Message | Thomas Flatley | 2021-01-05 21:55:00 | RE: Max# of tablespaces |