Comments on: PostgreSQL Sharding: An Overview and MongoDB Comparison https://www.percona.com/blog/an-overview-of-sharding-in-postgresql-and-how-it-relates-to-mongodbs/ Mon, 29 Apr 2024 13:23:33 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: AurĂ©lien LEQUOY https://www.percona.com/blog/an-overview-of-sharding-in-postgresql-and-how-it-relates-to-mongodbs/#comment-10974300 Mon, 29 Apr 2024 13:23:33 +0000 https://www.percona.com/blog/?p=57306#comment-10974300 It’s look like spider of MAriaDB =)

]]> By: Jeremy Holovacs https://www.percona.com/blog/an-overview-of-sharding-in-postgresql-and-how-it-relates-to-mongodbs/#comment-10974092 Fri, 16 Jun 2023 18:36:21 +0000 https://www.percona.com/blog/?p=57306#comment-10974092 Very interesting. I hope the future of sharding will allow more dynamic assignments. In the SaaS space, regulatory commitments require most services that process PII or other customer data to remove such data from their system completely in a timely manner, and I don’t see this business need being well addressed in the market today.

Consider a multi-tenant SaaS solution where you can include a tenant_id column on every table. We should be able to set “defaults” for db storage that allows for the creation of a new partition in a new remote file to store this data. Likewise, should the customer terminate the relationship, it should be a simple matter of dropping that remote file… but we’re still pretty far from that, it looks like.

]]> By: N https://www.percona.com/blog/an-overview-of-sharding-in-postgresql-and-how-it-relates-to-mongodbs/#comment-10972268 Wed, 27 May 2020 12:03:37 +0000 https://www.percona.com/blog/?p=57306#comment-10972268 Thanks for this info. Quite useful.

]]> By: Anthony https://www.percona.com/blog/an-overview-of-sharding-in-postgresql-and-how-it-relates-to-mongodbs/#comment-10970841 Wed, 29 May 2019 09:18:19 +0000 https://www.percona.com/blog/?p=57306#comment-10970841 Do you known the extension Citus ? https://www.citusdata.com/

]]> By: Kay Agahd https://www.percona.com/blog/an-overview-of-sharding-in-postgresql-and-how-it-relates-to-mongodbs/#comment-10970833 Mon, 27 May 2019 14:13:14 +0000 https://www.percona.com/blog/?p=57306#comment-10970833 Well written and very interesting, thank you! However, you write:
“It only ever makes sense to shard if the nature of the queries involving the target table(s) is such that distributed processing will be the norm […] Due to the distributed nature of sharding such queries will necessarily perform worse if compared to having them all hosted on the same server.”
While I fully understand your point, I wonder why it shouldn’t be beneficial to have less data on each shard. So even if the query hits every shard, each shard has to work through fewer data (for 10 shards only one-tenth). Of course, to be beneficial, it requires that the query is sent to all shards in parallel, which is not yet implemented in PostgreSQL as you wrote at the very end of your article – but I think it will be implemented in a near future and already is the case for mongoDB since its early days.

]]>