Pg_shard – PostgreSQL extension to scale out real-time reads and writes
1–10 of 28 posts
Re: Pg_shard – PostgreSQL extension to scale out real-time reads and writes
#2I wonder how it compares to the slightly more well established Postgres-XL.
There is definitely a different approach being taken as Postgres-XL has a supervisor/loadbalancer, and pg_shard seems like every node is capable of doing all actions.
Excited to see it evolve.
Re: Pg_shard – PostgreSQL extension to scale out real-time reads and writes
#3Gotta love how they opensource bits of their product.
Re: Pg_shard – PostgreSQL extension to scale out real-time reads and writes
#4This is another evidence of how extensible and flexible is PostgreSQL. Great work!
Re: Pg_shard – PostgreSQL extension to scale out real-time reads and writes
#5I wonder how it compares to the slightly more well established Postgres-XL. There is definitely a different approach being taken as Postgres-XL has a supervisor/loadbalancer, and pg_shard seems like every node is capable of doing all actions. Excited to see it evolve.
Postgres-XL has cluster-wide transaction support, this doesn't.
Re: Pg_shard – PostgreSQL extension to scale out real-time reads and writes
#6Comparing this a bit with Postgres-XL, how mindful of data locality do I have to be when querying? Looks like this drops right in for existing apps, but I'd be concerned about long-term performance if I didn't tailor my app code.
Re: Pg_shard – PostgreSQL extension to scale out real-time reads and writes
#7I wonder how it compares to the slightly more well established Postgres-XL. There is definitely a different approach being taken as Postgres-XL has a supervisor/loadbalancer, and pg_shard seems like every node is capable of doing all actions. Excited to see it evolve.
Postgres-XL has cluster-wide transaction support, this doesn't.
And cluster wide JOINs as well.
Re: Pg_shard – PostgreSQL extension to scale out real-time reads and writes
#8Having a master node which delegates all the queries sounds like a single point of failure. Could this be avoided by having a failover master?
Re: Pg_shard – PostgreSQL extension to scale out real-time reads and writes
#9Comparing this a bit with Postgres-XL, how mindful of data locality do I have to be when querying? Looks like this drops right in for existing apps, but I'd be concerned about long-term performance if I didn't tailor my app code.
You don't need to worry much about data locality with pg_shard. It's designed to push the computation to the data, and as such, abstracts away most data locality concerns. The only exceptions are complex analytic workloads such as distributed joins; and CitusDB offers an easy upgrade path to remove those concerns.
Another difference with Postgres-XL is that pg_shard is an extension to PostgreSQL, rather than a separate product with different components. As such, you can just compile and load it into standard Postgres, and you're ready to go.
Re: Pg_shard – PostgreSQL extension to scale out real-time reads and writes
#10It's great to see this released as open source (LGPL) -- looks like a really useful extension.
I've always been a fan of using PostgreSQL wherever possible, and this extends "where possible". As a YC S11 batchmate especially, I'm really proud of all the great contributions Citus Data has made, and what a useful tool CitusDB is (a bunch of other YC companies use it).