Re:Our Multi-Tenancy Journey with Postgres Schemas and Apart...
by eternalban on Tuesday December 06, 2016 @10:24AM
(#13115211)
> including a separate database server for every client ..
.. is actually a kind of "[h]andling this on the application level", with "this" being the Postgres' process management. Each database gets its own daemon and it is this per-database process that is responsible for launching a peer process for each connection.
There are likely legitimate use cases for multiple PG databases per node, but multi-tenancy is not one of them.
.. is actually a kind of "[h]andling this on the application level", with "this" being the Postgres' process management. Each database gets its own daemon and it is this per-database process that is responsible for launching a peer process for each connection.
There are likely legitimate use cases for multiple PG databases per node, but multi-tenancy is not one of them.