> > To my knowledge PostgreSQL doesn't support sharding, which is well and
> >
> > good because sharding is mostly useless, at least in my opinion.
> Not only does PostgreSQL natively support table partitioning (which is
>
> absolutely a form of sharding), there multiple well-regarded extensio
Mladen Gogala wrote on 11/30/21 7:52 PM:
To my knowledge PostgreSQL doesn't support sharding, which is well and
good because sharding is mostly useless, at least in my opinion.
OK I'll bite.
Not only does PostgreSQL natively support table partitioning (which is
absolutely a form of shardin
Saurav Sarkar wrote on 11/30/21 7:08 PM:
So are all the schemas on one DB or are distributed/sharded across
multiple DBs ?
In our use case, every db entirely homes one or more schemas. Some dbs
host many schemas for small customers, some dbs host a handful of
schemas for medium customers, and s
Store a connection string for each tenant or the metadata to build one on
demand. Then each tenant is in its own schema on whatever database instance
the connection string points at. Then it doesn’t really matter how you spread
your tenants across one database or many; just do whatever works b
On 11/30/21 22:08, Saurav Sarkar wrote:
Hi Ben,
Thanks a lot for your reply.
So are all the schemas on one DB or are distributed/sharded across
multiple DBs ?
Best Regards,
Saurav
To my knowledge PostgreSQL doesn't support sharding, which is well and
good because sharding is mostly useles
Hi Ben,
Thanks a lot for your reply.
So are all the schemas on one DB or are distributed/sharded across multiple
DBs ?
Best Regards,
Saurav
On Tue, Nov 30, 2021 at 11:43 PM Ben Chobot wrote:
> Saurav Sarkar wrote on 11/29/21 10:13 PM:
>
> Hi All,
>
> We have some multi-tenant solutions which
Saurav Sarkar wrote on 11/29/21 10:13 PM:
Hi All,
We have some multi-tenant solutions which are separating the tenant
data in Postgresql mainly in the following manner.
1. Using different schemas
2. Using different tables for different tenants.
Without more details it's impossible to give y
Hi All,
We are using Amazon RDS PostgreSQL.
We have some multi-tenant solutions which are separating the tenant data in
Postgresql mainly in the following manner.
1. Using different schemas
2. Using different tables for different tenants.
I was just wondering what would be the best way to scale
