News for hackers. Stuff that matters.
Re:It is done, the PostgreSQL community rocks by spacemanmatt on Wednesday April 05, 2017 @10:40AM (#14042386)
That is what people think they want when they do not understand the tradeoffs involved, typically.
Re:It is done, the PostgreSQL community rocks by user5994461 on Wednesday April 05, 2017 @01:56PM (#14044076)
There can't be high availability if there is only ever one node that accepts writes.

There can't be sharding if there is only ever one node that performs writes.

Re:It is done, the PostgreSQL community rocks by redwood on Wednesday April 05, 2017 @09:05PM (#14047119)
I'm genuinely curious what you mean here when you say high availability? Do you mean that during a distributed consensus failover timeframe, it is unacceptable for writes to be queued at the client?
Re:It is done, the PostgreSQL community rocks by user5994461 on Thursday April 06, 2017 @08:16AM (#14049849)
It means that the system is still available when one node is dead.
Re:It is done, the PostgreSQL community rocks by redwood on Wednesday April 05, 2017 @09:09PM (#14047136)
When you say that there can't be sharding without more than one one node taking writes, I totally see where you're coming from. And I agree with you. Typically that means that there is a logical isolation between which data goes to which shard so this avoids conflicts too. Usually when people talk about "multimaster" I do not believe they're thinking of this particular scenario but I may be wrong. I'm not familiar but does postgres not shard?
Re:It is done, the PostgreSQL community rocks by user5994461 on Thursday April 06, 2017 @08:19AM (#14049861)
There are two cases of multi-master.

- All nodes have all data (no sharding).

- No nodes have all data (sharding).

Re:It is done, the PostgreSQL community rocks by bsg75 on Wednesday April 05, 2017 @10:52AM (#14042484)
Multi-master works wonderfully until it does not. Then you have a terrible mess of inconsistent data.