News for hackers. Stuff that matters.
Re:Ask HN: It's 2023, how do you choose between MySQL and Po... by Volundr on Thursday May 11, 2023 @04:34PM (#35908021)
FWIW while I use Postgres for my own development I've had to administer a number of MySQL servers for other devs. Upgrades have always been updating the MySQL package, restarting MySQL, then running `mysql_upgrade`, and restart the server again. I'm pretty sure the mysql_upgrade has even been missed a number of times and it's worked fine.

I won't say it's impossible you ran into issues doing this, but it is the documented and supported upgrade path.

I love Postgres, but as someone whose maintained both for years, upgrades (at small scale) are the one area where I'd say MySQL has Postgres beat.

Re:Ask HN: It's 2023, how do you choose between MySQL and Po... by dijit on Friday May 12, 2023 @01:29PM (#35919250)
as long as you upgrade with a minor version, you will have the same experience with postgres.

11.0->11.2 will work totally fine, with no command needed.

Re:Ask HN: It's 2023, how do you choose between MySQL and Po... by Volundr on Saturday May 13, 2023 @03:44PM (#35931985)
Right, but now go from 11->12, which is the equivalent of the upgrade path I was describing for MySQL. I either need to install both versions and use pg_upgrade to convert the binary files, then remove 11 (and extensions may break this flow) or do pg_dump/restore.

Minor versions on both Postgres and MySQL are painless, just install and restart the server. Major upgrades on MySQL are significantly less painful.