Postgres couldn't support eventual consistency even if it wanted to. You're barking up the wrong tree. And you're barking at a strawman. Nobody was talking abo

Postgres couldn't support eventual consistency even if it wanted to. You're barking up the wrong tree. And you're barking at a strawman. Nobody was talking about eventual consistency. I don't disagree You could do that less verbosely then. The real problem to solve is dynamic promotion/demotion of masters This whole thread is about how postgres hasn't even streamlined the manual promotion/demotion of one master in a simple master/slave pairing.