Search Postgresql Archives

Re: PG Sharding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks Thomas.

Still fancying the manual approach litlle bit more.  

Will probably go with 8 database and 32 schema per machine. This way, will keep in limits for administration tools as well as autovacuum, also will be ready for connection pooling, as 8 databases is not to much. 

This will give us 256 shard per machine, but will be tunable. The lower number will also prevent to much memory/disk fragmentation and with this bad cache hit ratios.

Will also use monthly partitioning per shard, to reduce the change of big tables forming. 

Thanks everyone.


2018-01-30 15:26 GMT+01:00 Thomas Boussekey <thomas.boussekey@xxxxxxxxx>:
Using citusdb enterprise, you can replicate the table shards.

Regards,
Thomas


2018-01-30 12:18 GMT+01:00 Matej <gmatej@xxxxxxxxx>:
As already said. It's missing 2 level sharding and is restricted with SPOF.

BR

Matej

2018-01-30 12:05 GMT+01:00 Rakesh Kumar <rakeshkumar464@xxxxxxx>:



>We are looking for multi tenancy but at scale. That's why the sharding and partitioning. It depends how you look at the distributed part. 

Citusdb.




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux