News for hackers. Stuff that matters.

A comment on PostgreSQL HA cluster failure: a post-mortem. Parent comment

Re:PostgreSQL HA cluster failure: a post-mortem by antoncohen on Wednesday December 06, 2017 @01:58PM (#15863833)
I don't think the claim of MySQL replication being better is related to statement vs. row vs. binary diff. I think it is about the tooling and community knowledge about replication, and about running MySQL in large scale production environments in general.

MySQL is run more often at extremely large scale (Facebook, YouTube, Twitter, Dropbox, etc.) than Postgres. That results in very battle tested and/or featureful tooling like orchestrator (https://github.com/github/orchestrator), MHA (https://github.com/yoshinorim/mha4mysql-manager), ProxySQL (http://www.proxysql.com/), and gh-ost (https://github.com/github/gh-ost), along knowledge and best practices shared by those organization.

[ Parent | on HN ]
Re:PostgreSQL HA cluster failure: a post-mortem by amigoingtodie on Wednesday December 06, 2017 @07:46PM (#15866591)
What are anybody's real-world use case for proxysql?

I have been toying with the idea of using it for local devs to access our prod DB for reads (for accurate data) and using a local DB on their machines for writes.

Not sure how to handle UPDATEs, though.

[ Parent | on HN ]
Re:PostgreSQL HA cluster failure: a post-mortem by emfree on Wednesday December 06, 2017 @09:12PM (#15867053)
Use cases for ProxySQL: many.

- failover

- query routing (e.g., for sharded deployments)

- caching

- workload stats/metrics

- query rewriting

etc.

[ Parent | on HN ]