Assigned
Status Update
Comments
fa...@google.com <fa...@google.com> #2
Hello Mike,
Thank you for the suggestions. I would like more information about the sharding feature you are requesting. Is it possible to explain more about your use case?
Thank you for the suggestions. I would like more information about the sharding feature you are requesting. Is it possible to explain more about your use case?
mh...@dinkusa.com <mh...@dinkusa.com> #3
Sure, we're aggregating lots of different data from across the web, and we anticipate that eventually our database will outgrow a single instance and require sharding to perform as needed.
fa...@google.com <fa...@google.com> #4
Mike,
I forwarded your feature request to the product team. You can track this thread for any updates, or post additional comments about the request. However, we can not provide an ETA or guarantee its implementation at this point in time.
Thank you again for the suggestions.
I forwarded your feature request to the product team. You can track this thread for any updates, or post additional comments about the request. However, we can not provide an ETA or guarantee its implementation at this point in time.
Thank you again for the suggestions.
co...@gmail.com <co...@gmail.com> #5
Can somebody please add this feature. It is a much needed feature to support sharding. Unable to do shard because of this. Azure has bought citus for the same purpose.
[Deleted User] <[Deleted User]> #6
Me, too!
FWIW, Citus is a PostgreSQL extension that add these 4 features to Postgres:
- Columnar storage compresses data, speeds up scans, and supports fast projections, both on regular and distributed tables.
- Distributed tables are sharded across a cluster of PostgreSQL nodes to combine their CPU, memory, storage and I/O capacity.
- References tables are replicated to all nodes for joins and foreign keys from distributed tables and maximum read performance.
- Distributed query engine routes and parallelizes SELECT, DML, and other operations on distributed tables across the cluster.
Of the 4 features, Columnar storage engine (https://github.com/citusdata/cstore_fdw ) is the most desirable.
Reference:
-https://en.wikipedia.org/wiki/Column-oriented_DBMS
-https://www.citusdata.com/blog/2014/04/03/columnar-store-for-analytics/
-https://www.citusdata.com/blog/2021/03/06/citus-10-columnar-compression-for-postgres/
FWIW, Citus is a PostgreSQL extension that add these 4 features to Postgres:
- Columnar storage compresses data, speeds up scans, and supports fast projections, both on regular and distributed tables.
- Distributed tables are sharded across a cluster of PostgreSQL nodes to combine their CPU, memory, storage and I/O capacity.
- References tables are replicated to all nodes for joins and foreign keys from distributed tables and maximum read performance.
- Distributed query engine routes and parallelizes SELECT, DML, and other operations on distributed tables across the cluster.
Of the 4 features, Columnar storage engine (
Reference:
-
-
-
rj...@google.com <rj...@google.com> #7
+1
I have a customer who is building a multi-tenant product in a way that it can easily scale horizontally.
Citus is a well known, open source solution that helps make that possible.
If citus cannot be supported in GCP, they will look at azure since it is already supported there.
ja...@csiro.au <ja...@csiro.au> #8
Citus would be a fantastic suite of tools to be able to extend postgres. It is also supported on Azure.
+1
+1
Description