I agree - it requires a re-think/re-build As for oracle, quite easy to add tablepaces in flight, assuming you don’t hit max db_files
I was more curious if there was an actual defined limit - oracle stops at 64K , and their old application release would have 2tbsp per module, and at 400 or so that’s a hassle -----Original Message----- From: Christophe Pettus <x...@thebuild.com> Sent: Tuesday, January 5, 2021 5:02 PM To: Thomas Flatley <flatl...@outlook.com> Cc: Andreas Kretschmer <andr...@a-kretschmer.de>; pgsql-general@lists.postgresql.org Subject: Re: Max# of tablespaces > On Jan 5, 2021, at 13:55, Thomas Flatley <flatl...@outlook.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 x...@thebuild.com
