What's the best DBMS for the job?
It just discussed the benefits of using PostgreSQL over MySQL and vice versa. Does anyone have any practical experience when there is a good reason to use one over the other?
Some people have said that Postgre is better for security whereas MySQL is getting more feature rich ... I'm not sure what to do with it.
source to share
The question is not which is better, but which is better suited for the specific use you intend.
If you don't need transactional consistency, mySQL can provide better performance. If you do this, PostgreS may be faster. If you need spatial search, PostgreS. Tables larger than 2 GB, PostgreS. Bitmap indexes, PostgreS. INTERSECT, PostgreS.
... it can go on ad-nauseum. And then we get to the "best" question, and that assumes that mySQL or PostgreS are only two options. Sometimes SQLite is the best. Or Oracle. Or even some storage engine that is not an RDBMS.
(and note that I said that "may" give better performance - just because one is usually faster doesn't mean it will be faster for how you underline it)
source to share
It can also depend on your point of view ...
If you were an employer, you would like to ensure the adoption rate is as fast as possible so you can find developers who can work for it.
If you're a developer, features, documentation, and the community are important.
If you are an architect, security, features, and scalability are important.
If you are an end user. You don't care!
source to share
The simple answer is that postgres is better suited for both functionality and security.
However, MySQL is much more popular, so it is more likely that it will be directly supported by a random application, especially web applications. MySQL also makes statements faster (perhaps because it has fewer features).
Thousands of web pages are dedicated to this topic.
source to share
I have used both and even migrated projects from MySQL to PostgreSQL and in my experience PostgreSQL was the best choice. For my applications, it was at least on par with MySQL and offered the necessary features not found in MySQL. That being said, if MySQL suits your needs, this is a nice little dbms and like other dbms keeps getting better.
source to share
Could write a new answer here, but there are so many existing ones that are hard to take care of:
- Is MySQL suitable for database readable with 3.5m + rows?
- MySQL vs Postgresql pros / cons for creating Ruby on Rails environment?
- Best database engine for huge datasets
- Postgres or MySQL for web applications
- MySQL vs. PostgreSQL for Web Applications
- Why is PostgreSQL not as widespread as MySQL?
- How does PostgreSQL differ from MySQL?
source to share
If you are using a DBMS for a website without any transactional needs - your choice is MySQL with the MyISAM engine. If you are developing more industrial software then PostgreSQL. PostgreSQL's awesome feature writes stored procedures in different languages not only PL / PgSQL. There could be C, Python, PERL ... whatever you want and for which a language handler exists.
source to share