Imagine you are starting a new project, and your backing datastore options are restricted to mysql or postgres (and/or their cloud-tailored equivalents.) What sort of functional requirements would cause you to choose one over the other?
Ask HN: It's 2023, how do you choose between MySQL and Postgres?
1–10 of 366 posts
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#2We choose Postgres for extensibility and stability :)
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#3I dunno if this is still true but a couple of years ago MySQL was cheaper on AWS (RDS/Aurora) than Postgres.
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#4Also interested in the responses, not because it seems like a close decision but because I would pick postgres by default for anything (anything that isn't simple enough to be done in sqlite).
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#5Pick postgres unless you have a good reason not too?
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#6We choose Postgres for extensibility and stability :)
I was going to make a similar joke: you look at them and choose Postgres
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#7You choose postgres.
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#81) The choice is Postgres if you care about your data at all.
2) Yes, if you are already HUGE and have requirements on Vitesse then by all means use it. If so, you are not asking this question—see #1.
3) It's a blog or something where it doesn't matter, use a static site generator.
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#9MySQL for the quick and dirty and Postgres for anything else
Re: Ask HN: It's 2023, how do you choose between MySQL and Postgres?
#10If Postgres was that much better than MySQL then you would expect to see exact reasons on why to pick it. Every comment so far has not listed any reason.