Yes, but MariaDB, mostly DIY on localhost (various test & live VMs I manage).
Most painful? Replication with automatic failover could be easier to setup. Considering switching to MySQL 8.x for the new-ish innodb cluster tools (mysqlsh, mysql-router).
Why not Postgres? Familiarity, mostly using it for Drupal & Wordpress sites where MySQL is king. Besides the occasional poorly-designed query that eats memory and causes timeouts, MySQL rarely needs my attention.
Side note: I'm excited for https://github.com/mydumper/mydumper. Multi-threaded logical backups, 2 to 5 times faster than mysqldump. It's not super stable yet, so we haven't been relying on it for long term backups, but doing a "mydumper to grab a schema on live, rsync down to laptop, myloader to import" it's been a big time saver.
Most painful? Replication with automatic failover could be easier to setup. Considering switching to MySQL 8.x for the new-ish innodb cluster tools (mysqlsh, mysql-router).
Why not Postgres? Familiarity, mostly using it for Drupal & Wordpress sites where MySQL is king. Besides the occasional poorly-designed query that eats memory and causes timeouts, MySQL rarely needs my attention.
Side note: I'm excited for https://github.com/mydumper/mydumper. Multi-threaded logical backups, 2 to 5 times faster than mysqldump. It's not super stable yet, so we haven't been relying on it for long term backups, but doing a "mydumper to grab a schema on live, rsync down to laptop, myloader to import" it's been a big time saver.