Hacker News Reader

Comment by vruiz | Hacker News Reader

> I think there is only one place where RethinkDB is better then PostgreSQL: replication + automatic failover.

I was about to ask. Are you guys running a single server deployment? Because, while I haven't used RethinkDB yet, it appeals to me precisely because PostgreSQL is an absolute pain to operate beyond single node setups. I've heard citusdb tries to tackle this, I don't know if they succeeded but still it doesn't look nearly as friendly as RethinkDB.

View on HN

We don't need to shard our data, but we do multiple node setup for HA using Pgpool + streaming replication.

From what I heard sharding my be really problematic, and one should avoid it as much as possible.

I tried pg_shard a few months ago and after a few hours, I gave up. I somehow remember that partitioning MySQL was easier, and that's not a compliment.

Yes, we moved to galera cluster. Even with its random node shutdowns, from my second-hand impressions it's still better than dealing with the pgpool, slony, et al.

Sumedh from Citus Data here. I'd love to hear what difficulties you ran into, or any feedback you may have on pg_shard. My email is in my profile if you want to drop me a note.

We are also actively working on making our products easier to use and would love to get more user input along that way.

It was mostly a lack of docs. Most of the documentation assumes citusDB, and how to get things work without citusDB is left out.

Reply on news.ycombinator.com