Re:Pg_shard – PostgreSQL extension to scale out real-time re...
by deedubaya on Thursday December 04, 2014 @01:19PM
(#8700727)
Having a master node which delegates all the queries sounds like a single point of failure. Could this be avoided by having a failover master?
[ Parent
| on HN ]
Re:Pg_shard – PostgreSQL extension to scale out real-time re...
by jasonmp85 on Thursday December 04, 2014 @01:40PM
(#8700858)
Hey, Jason from Citus Data here (one of pg_shard's authors).
Yes: if you have high availability needs, PostgreSQL's streaming replication feature can mitigate this failure risk by providing a hot standby for your master; otherwise, regular backups of the master can suffice (pg_shard's metadata is stored in regular PostgreSQL tables).
See our documentation page for more answers to questions like this: http://citusdata.com/docs/pg-shard
Re:Pg_shard – PostgreSQL extension to scale out real-time re...
by gunnark01 on Friday December 05, 2014 @02:46AM
(#8703357)
We have something similar in house, it is basically proxy that runs on our app-server and our app connects to. It will then parse incoming queries and route queries to the correct schema/server base on the WHERE clause (also supports INSERT). We would like to on open source it, but right now it specific to our needs (e.g hard coded hash function).