MySQL vs PostgreSQL
wikivs.com
MySQL vs PostgreSQL
1–10 of 27 posts
Re: MySQL vs PostgreSQL
#2Flamewar in 3... 2... 1...
Oh... This is not Slashdot. Sorry.
Re: MySQL vs PostgreSQL
#3If you're in Portland this weekend and want to learn something about Postgres then you should attend http://pgcon.us/ Postgres West.
Re: MySQL vs PostgreSQL
#4This is very useful (although I am not qualified to say if it's definitive or not). I chose PostgreSQL based on one single fact that I ONCE crashed a MySQL server with a query (about 4 years ago) and I've never crashed PostgreSQL.
It's a flimsy reason tbh but it's all I had to go on. Having said all that I do really love PostgreSQL now after 4 years of using it (via SQLAlchemy).
Re: MySQL vs PostgreSQL
#5I don't understand why MySQL has 9 different storage engines.
Would someone mind quickly posting the benefits of that architecture as opposed to focusing on one 'storage engine' and making it really good?
Re: MySQL vs PostgreSQL
#6I don't understand why MySQL has 9 different storage engines. Would someone mind quickly posting the benefits of that architecture as opposed to focusing on one 'storage engine' and making it really good?
I think the argument is that different domains impose different requirements on the storage engine. The type of data organization I would like to use for a read-mostly web application vs. an OLTP-type transaction processing workload vs. an OLAP-type analysis workload might all differ fairly substantially.
Re: MySQL vs PostgreSQL
#7We switched from MySQL to PG when mysql suddenly returned different results in a unit test when we upgraded to a newer minor version. Never looked back.
Re: MySQL vs PostgreSQL
#8This is very useful (although I am not qualified to say if it's definitive or not). I chose PostgreSQL based on one single fact that I ONCE crashed a MySQL server with a query (about 4 years ago) and I've never crashed PostgreSQL. It's a flimsy reason tbh but it's all I had to go on. Having said all that I do really love PostgreSQL now after 4 years of using it (via SQLAlchemy).
I tend to chose PostgreSQL because of the query language. It is more comfortable to program in.
As ORMs become more prevalent, things like query language start to become less relevant, but so do relational databases. I really don't care how my data is stored, as long as it's safe and performs well.
Re: MySQL vs PostgreSQL
#9I don't understand why MySQL has 9 different storage engines. Would someone mind quickly posting the benefits of that architecture as opposed to focusing on one 'storage engine' and making it really good?
Well, I pose to you this question:
Would you rather have 1 type of car that the government makes that works pretty reliably and is a middle-ground car, or would you rather have a selection of cars to chose from; sports, truck, sedan, minivan, etc. ?
Everyone has different needs. I use MySQL extensively for it's memory-based storage engine, MyISAM for quick & dirty non-escential data i/o, and InnoDB for when data needs to be managed securely for processes.
I would use PG for transaction-based data processing in a high-volume situation with multi-processing clusters. Otherwise MySQL works fantastic for all my needs.
Re: MySQL vs PostgreSQL
#10OTOH I was thinking about moving my app from MySQL to SQLite. Did anyone else has gone through the same situation?