Scaling out relational data models, and SQL, through co-location

Re:Scaling out relational data models, and SQL, through co-l... by ahachete on Saturday December 24, 2016 @06:56AM (#13249472)

First of all, every database comes with some metadata overhead (catalog tables) which amounts to ~ 30MB. Take into account that this also may (should!) be in memory (shared_buffers) so it can become expensive.

But the most significant factor is whether you need to do queries that span multiple users/tenants. If you need to, you will require postgres_fdw and nor performance neither manageability will be good at all.

[ Parent | on HN ]

Re:Scaling out relational data models, and SQL, through co-l... by paulddraper on Sunday December 25, 2016 @01:51PM (#13255015)

> need to do queries that span multiple users/tenants

If you need that, shouldn't you use one database?

[ Parent | on HN ]

Re:Scaling out relational data models, and SQL, through co-l... by raarts on Saturday December 24, 2016 @04:02PM (#13251608)

If you use it for multi tenanting then probably you won't need that.

But 30MB is a lot yes.

[ Parent | on HN ]