Hacker News Reader

Comment by kstrauser | Hacker News Reader

To be fair to PostgreSQL, it has multiple replication setups because they have different inherent properties. For instance, it comes with built in streaming and logical replication setups. Which should you use? It’s impossible to say without knowing your own exact use case.

By analogy: should a database cluster optimize consistency or availability? Answer: there’s no way its author can guess which is more important to how you want to use it.

View on HN

MySQL/MariaDB have binary and logical replication too. They also support much more advanced topologies like multi-master out of the box. It's just that what you need for 99% of situations relies on a well trodden path and requires no configuration at all.

I have suspected for a long time that most people who criticize MySQL have never actually worked with it, or have done so a couple of decades ago. It's often the default choice if you don't need some of the PostgreSQL features (like PostGIS) and can work with either one.

> They also support much more advanced topologies like multi-master out of the box.

This is the one thing in My/MariaDB that I miss in Pg: Galera. So handy for in-house stuff that needs some kind of HA: either a three-server setup, or a two-server+arbitrator.

Try https://pg-auto-failover.readthedocs.io/en/main/intro.html

I haven’t used Galera, but I am very happy with https://patroni.readthedocs.io/en/latest/ for Postgres.

MySQL has only logical replication, there is no equivalent to PostgreSQL‘s WAL/physical replication.

Since v16, Postgres supports bidirectional logical replication out of the box. In other words, multiple writers.

The same is true for MariaDB so I have no idea what he is talking about. Both databases have multiple options.

Reply on news.ycombinator.com