new | show | ask | jobs Github

evanelias 3 hours ago

A few major areas where MySQL/MariaDB excels:

Threaded connection model (no process spawning)

Undo-based MVCC (no need for vacuum)

InnoDB's use of a clustered index for PK (has pros/cons, but better for some workloads)

Ability to use alternative storage engines such as MyRocks (LSM based instead of B-tree; best-in-class compression)

Support for index hints (so query plans won't randomly change and bring your site down)

More mature logical replication (fully supports DDL, has no concept of limited "replication slots", etc)

That all said, there are also many areas where Postgres is better! Like all things in computer science, there are architectural trade-offs, and no single silver bullet is the best choice for all workloads.

▲

waynesonfire 2 hours ago | parent [-]

Your list confirms that MySQL is irrelevant to me.

	▲	direwolf20 2 hours ago \| parent \| next [-]
		Why act so snobbish about it? They're both cromulent databases. You should try doing one project with each. The converse of this list would tell the diehard postgres user that mariadb is irrelevant to him. They have quite different internal design, this affects what features are possible. No clustered index in postgres for instance, and UPDATE can reorder rows, but it supports replication much better.
	▲	evanelias 2 hours ago \| parent \| prev [-]
		That's totally fine, there are many workloads where Postgres is the best choice! I'm not forcing you to use it, I was just responding to the comment upthread about lack of advantages. It's kind of bonkers that the anti-MySQL crowd is so rabid that any attempt to explain legitimate use-cases for MySQL is met with a barrage of downvotes, especially in a submission that is directly about MySQL specifically :/