Ask HN: Any one still using MySQL? Do you manage your own MySQL installation?
- If not, what managed provider do you use?
- Either way, what’s your biggest pain point? Why not Postgres? |
Ask HN: Any one still using MySQL? Do you manage your own MySQL installation?
- If not, what managed provider do you use?
- Either way, what’s your biggest pain point? Why not Postgres? |
Yes, but more so MariaDB
> Do you manage your own MySQL installation?
Yes and no, depends on the environment.
> what managed provider do you use?
RDS
> what’s your biggest pain point?
Nothing initially comes to mind.
> Why not Postgres?
Habit? It's what I learned with and just kept using. I understand it's permission model better than Postgres. I know how to back it up, restore, and replicate. At one time (not sure if this is still the case) it was noticeably cheaper than Postgres in AWS for our use cases.
Some legacy systems can't be migrated to postgres even if we wanted.
I've used Postgres and it has some nice features, especially with it's data types but often find myself lost with it's way of doing things. When possible I reach for SQLite instead of MySQL.
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.
We've never seen the point of converting to postgres, a lot of work for little if any gain?
No strong reasons for it, but I wanted to try psql after decades of toying with MySQL. I like it despite its weird insistence on snake case for everything.
Biggest pain points are pretty much transactions around schema changes (Ruby on Rails context) meaning is possible to trash a database with changes that go wrong. Also implementing full text search is always a bit harder than it is with PostgreSQL. The capability is there but end up having to do custom queries.
Planetscale
Lack of simple HA in Citus is a big pain point.