Always PostgreSQL. Unless if MySQL protocol is absolutely needed.
Ask HN: It's 2023, how do you choose between MySQL and Postgres?
101–110 of 366 posts
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#102Choose whichever one you/your team is more familiar with. Both are battle-tested and proven and will likely scale to whatever needs you have.
And if you have experience with one and try to use the other, you may end up foot gunned by something you didn't know about.
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#103If you're a gigacorp you might have reasons to go with a customized version of MySQL otherwise pick Postgres.
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#104There is almost no good reason to choose MySQL over PostgreSQL for any operational reason, I did a deep dive many moons ago (before major improvements in performance to postgres) and people were saying that MySQL was faster. I found that not to be true and the differences have only gained even more favour towards postgres. also, I assume you mean MariaDB as MySQL is owned by Oracle and I would greatly implore anyone…
Is there a good way to do case-insensitive accent-insensitive collations yet in postgresql? It’s been a holdup for using that for some use cases like searching for data, like a person’s name, in pgsql when the casing or accents don’t match perfectly. Mssql has had this for ever, and I’m pretty sure MySQL has it as well.
Not really, no, it's doable but not easily
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#105Postgres. Fast, full-featured, rock-solid, and a great community. I think many of us can’t be bothered to go over (again) the issues we’ve had with MySQL in the past. The last straw for me was about ten years ago, when I caught MySQL merrily making up nonsense results for a query I’d issued that accidentally didn’t make any sense. Very likely this particular issue, and others like it, have been fixed in the meantime.…
Having used postgres for the past decade, I tried MySQL for a side project to see whats changed with it. The sad answer is that it feels like nothing has changed - Oracle seems to have let what used to be a core technology of the industry languish.
I'm sure there are use cases where MySQL will be the better choice over postgres, but the future for the stack looks bleak.
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#106I don't use either but I don't think I've seen MySQL mentioned in any meaningful way in almost a decade at this point. If forced, knowing only that, I'd choose postgres.
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#107Choose whichever one you/your team is more familiar with. Both are battle-tested and proven and will likely scale to whatever needs you have.
This is the correct answer. Whichever one you start out with, you will be annoyed if you switch to the other one 5 years later. I started out with mysql, and when I started working on a postgres project, I was shocked at some of the ways it was lacking (how am I supposed to store email addresses in a database without collations?). But when postgres folks grouse about stuff in mysql, I'm usually nodding along and sayi…
> when I started working on a postgres project, I was shocked at some of the ways it was lacking (how am I supposed to store email addresses in a database without collations?)
How long ago was this? :)
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#108Am I the only one who thinks postgresql’s timestamp and timestamptz types are incredibly stupid?
I just want to either save a local date and time, or an utc timestamp. Postgresql’s timestamp(tz) types do neither and both at the same time.
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#109Unpopular opinion on HN apparently, but MySQL
- It's less featureful, and I'd consider that a strong virtue in the YAGNI camp - less to go wrong, less mental overhead.
- Maintenance is simpler and far less necessary in my general experience.
- Replication is simpler and more reliable.
- You can tell the query optimizer what to do. When this is needed, you'll be thankful. It's a godsend.
That said, I wouldn't run Oracle MySQL. I opt for MariaDB on smaller projects and AWS Aurora MySQL for larger projects. Aurora scales insanely well, and replication lag is almost non-existent.
In my general experience MySQL was always significantly faster but it's been a number of years since I've worked with Postgres and the comments here seem to indicate that that may no longer be the case. YMMV
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#110I've been using MariaDB (MySQL) as a hobbyist for years. I just set up a couple myqsql servers with phpmyadmin on Raspberry PIs and use them for local development. Basic crud apps, etc. I've always assumed that PostgreSQL is a step up, but never really bothered to look into what I get for the effort. Do I really get anything if I'm not trying to make apps at scale?
> I've always assumed that PostgreSQL, but never really bothered to look into what I get for the effort.
You're making a (mistaken) assumption that Postgres giving you a "step up" means that you also have to put in more effort. You don't, at least not in my experience. Both are database servers with a bunch of install & setup. There's phppgadmin if you want an 1:1 replacement for phpmyadmin (no opinion on these, haven't used either).
Postgres just gets you farther if you need to at a later point.
I would recommend you swap out mysql for postgres on your raspis. You're gaining experience on one of the two. But experience on Postgres seems to be more useful and valuable (cf. rest of the HN comments), for the same cost of your time.