[syntern]

Yes, there are billions of different setups, but there are a few basic ones, and you could start by solving one or two, before solving the generic case. For example, one could provide just a cluster setup for data replication. No fancy distributed data models, just copy the data around in the cluster, if a new node joins copy that data to it, if something fails, handle the failure. Postgresql claims to have multi-master setups, so this is really about the node handling and copying the data around.

After that, you could introduce locally distributed cluster. Later on you could introduce geographically distributed cluster setups. But just because the later is very complex, does not mean that you can't start with the basic setup.

[empthought]

> if something fails, handle the failure.

This generally involves halting the server or forcing a read-only mode until consistency can be assured.

But in general repmgr[1] can be used to simplify many common activities and configurations.

[1] http://www.repmgr.org

[imanaccount247]

Setting up the few basic ones is already as easy as it can get.

[ohyesyodo]

Synchronous replication with automatic failover?

[imanaccount247]

Yes.

[syntern]

Care to provide a link with the easy setup and cluster management? It could be a well-hidden gem that needs more publicity.

[imanaccount247]

https://wiki.postgresql.org/wiki/Replication,_Clustering,_an...

[ohyesyodo]

Trying to be ironic? That page does not present an easy way to set up what I asked for.