3 ms·
I'd say it depends on your team's level of knowledge on various DB's, the expertise available in your geographic area, and the expected size that your data set
by evanelias 10y ago
I'd say it depends on your team's level of knowledge on various DB's, the expertise available in your geographic area, and the expected size that your data set would grow to.
I'm not sure there is a "typical" workload in the general case ;)
Don't get me wrong; Postgres is a really really good piece of software with many appealing qualities. But its fanbase is a bit overly rabid, or at least over-eager to trash MySQL for things that haven't been true in years or never were true in the first place. There are some very valid MySQL complaints mixed in there too, but it can take some effort to separate them out...
- lima 10y agoThanks! Our team is definitely going to stick with MySQL (no reason not to) and I have no reason to hate it, but I always like these sort of comparisons since you learn a lot about the technology. I'm really interested in PostgreSQL for "real time OLAP" use cases with things like Citus - apparently, many companies use Citus in particular to run distributed analytics queries on their main database.
- i336_ 10y agoHmm. Have you seen any wholesale feature comparisons between the two that you'd consider objective and fair, and which debunk old myths in the process?
- evanelias 10y agoUnfortunately I haven't. People who are equally well-versed on both databases seem to be the rarest of unicorns.