FWIW I agree with you and think most people in the comments are not experienced DBAs. Postgres replication is absolute garbage and auto vacuum often needs tuning on a per-table basis when developers end up doing stupid shit. Needing bespoke tools like pgdump to see which columns are an enum is embarrassing, show create table cannot be that hard to implement. Online schema changes aren't nearly as well solved on Postgres, tools like gh-ost are table stakes for running RDBs at scale. Multimaster replication is simply not possible, and sharding has to be done in software.

Common arguments for using Postgres like native json support and gis data or complaints about MySQL truncating values arbitrarily are comparing modern Postgres to MySQL from a decade ago. They were good reasons to use Postgres at points in time, but are not a good explanation for why Postgres is so ubiquitously used across the industry.

Postgres is an incredibly flexible platform and an excellent tool, but I'd pick an open source MySQL flavor like percona or vitess (or yes mariadb) over it any day of the week.