Very good points. I'd add that PostgreSQL didn't even get built-in streaming replication until late 2010 so if you were evaluating anything for a high-availability setup before 2011, you'd be looking at MySQL. As you note, database choices tend to be sticky.
PostgreSQL's replication is still a bit of a pain and MySQL has things like Vitess that which offer great tools for scaling out a database (including sharding, replication, etc)
PostgreSQL has improved a lot from the 2000-2010 time period, but MySQL still has some good stuff going for it.
PostgreSQL's replication is still a bit of a pain and MySQL has things like Vitess that which offer great tools for scaling out a database (including sharding, replication, etc)
PostgreSQL has improved a lot from the 2000-2010 time period, but MySQL still has some good stuff going for it.