Also they didn't mention anything about the auto vacuumer, which mostly solved the issue they are talking about.
Their lack of mention of the vacuumer and not seeming to know that Postgres supports statement level replication makes me wonder if they took a deep dive into the wrong part of the technology.
On Postgres an update requires a rewrite of every index of the row.
On MySQL it only requires an update of the indexes that were touched by the update.
If you have a table with 10 indexes then this means doing 10 extra writes physically to the disk.
Please refer to 64~ page of https://momjian.us/main/writings/pgsql/mvcc.pdf.
There's been quite a few improvements to VACUUM in 9.6 [1], including avoiding full-table scans.
[1] https://www.postgresql.org/docs/9.6/static/release-9-6.html#...
Yes, there were some other points that were just extra annoyances for them but clearly that point was the most important to them. It's what the header image and the first 60% of the article was talking about and yet nobody seems to be engaging with that point in this thread.
Is the design choice bad? They never said it was. It's just an engineering trade off. It's very possible that most workloads benefit from this design. But if you workload involves updating lots of existing rows at large scale, then MySQL is going to be a better choice for you.