[eikenberry]

Any progress on high availability deployments yet? Or does it still rely on problematic, 3rd party tools?

Last time I was responsible for setting up a HA Postgres cluster it was a garbage fire, but that was nearly 10 years ago now. I ask every so often to see if it has improved and each time, so far, the answer has been no.

[porsager]

You should definitely give pg_auto_failover https://github.com/citusdata/pg_auto_failover/ a try. I've written about my experience here: https://github.com/citusdata/pg_auto_failover/discussions/61... which hasn't changed since..

[threeseed]

If you want HA use AWS RDS, Azure Citus, GCP Cloud SQL.

Otherwise use MySQL, Oracle, MongoDB, Cassandra etc if you want to run it on your own.

Any other database that invested in a native and supported HA/clustering implementation.

[tluyben2]

Cockroachdb or Yugabyte work well for some cases you might use postgres for.

[edoceo]

From the old days it's way better. Both Logical and streaming replication is only a few lines, few commands kind of thing.

Logical for streaming to read only replicas and streaming for fail-over. My client-app still needs to know try-A then try-B (via DNS or config)

[latch]

But there's so much more to it than this, e.g. upgrading, failing over, point in time recovery, monitoring.

I manage both a cockroachdb cluster and a few PG setups. Out postgres' have streaming replication to a standby with barman running on the standby. They are night and day.

Sure 2021 PG is way better than 2010 PG. But relative to available options, it's much worse.

[rusbus]

I found running a 6-node Patroni cluster on Kubernetes to be a surprisingly pain-free experience a couple of years ago

[tpetry]

I have been looking at patroni for years. But i still do not feel compatible using it in a production environment. If something fails it will be really really hard to fix it, but i have the same feeling for almost all these complex kubernetes operator doing a lot of magic work to have a simple solution.