Even with Oracle you need to know the architecture of your storage to decide whether you can expect performance improvements. If you happen to have some kind of NAS, you partitions for the different table spaces might reside on the very same hardware and you probably gain naught.
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, 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?
