We compared PostgreSQL and MySQL based on our user's reviews in several parameters.
PostgreSQL is known for its robustness, scalability, and efficiency, with excellent customer service. However, it requires improvements in performance optimization and installation processes. On the other hand, MySQL is valued for its data management efficiency and security measures, with outstanding customer support. Areas for enhancement include query execution speed and documentation.
Features: PostgreSQL users appreciate its robustness, scalability, advanced SQL functionality, extensive community support, and compatibility with multiple operating systems. Meanwhile, MySQL shines with its efficient data handling, flexibility, ease of use, and strong security measures.
Pricing and ROI: PostgreSQL offers a manageable setup cost and fair licensing terms, catering to various budgets. On the other hand, MySQL is praised for its affordable setup cost and flexible licensing options, making it a reasonable choice for users., PostgreSQL offers excellent scalability, security features, and integration with other systems, delivering reliable results. MySQL is praised for its reliability, cost-effectiveness, ease of use, and ability to handle large databases.
Room for Improvement: PostgreSQL has room for improvement in enhancing overall performance, addressing difficulties during installation and configuration, improving documentation, and enhancing the user interface. On the other hand, MySQL needs enhancement in performance, documentation, support channels, scalability, compatibility, and security features.
Deployment and customer support: Users of PostgreSQL reported that the deployment and setup of a new tech solution took either 3 months for deployment and an additional week for setup or 1 week for both phases. On the other hand, users of MySQL reported longer deployment durations, ranging from several months to 1 week for both deployment and setup., PostgreSQL's customer service and support have been praised for their responsiveness, helpfulness, and effectiveness. Users appreciate the prompt and knowledgeable assistance provided by the team. In comparison, MySQL's customer service and support are highly praised. Users appreciate the prompt and helpful assistance they receive when facing any issues or inquiries. The support team is described as knowledgeable and reliable.
The summary above is based on 35 interviews we conducted recently with PostgreSQL and MySQL users. To access the review's full transcripts, download our report.
"The IO segregation in CGE is valuable."
"A good traditional database that supports JSON."
"I like the simplistic view of MySQL to build custom queries and things like that as compared to SQL Server, which seems more cluttered. SQL Server has a query analyzer. MySQL pretty much does the same, and performance-wise, it has less overhead for connecting to our ERP system. It seems more responsive and cleaner. With MySQL, you get what you need without any overbloating, for which Microsoft is known. That's why they have so many constant security patches for everything because there is so much stuff, which degrades performance."
"What I've been most pleased with is the cost point, performance, and ease of use."
"The way that MySQL has improved my organization is that it comes free and also works fine on the technical side."
"The solution has been very easy to scale so far."
"This specific version of this MySQL has been battle tested for a long time. Any issues are known issues and we pretty much don't have any problems when they're in production. So it's very stable."
"The fact that it is free is what appeals to me the most."
"One of the most valuable features is real-time data capture; it optimizes database performance. I think using real-time data capture reduces job running time and the amount of data sent at once with batch loads."
"It has completely met our needs. It works, and it is robust. We haven't had any problems with what PostgreSQL does for us and the way it does it. That's why we've been using it for so long. We understand it, and it does the job."
"The initial setup is quick and easy."
"The most valuable features are the price, stability, it is scalable and is used by our clients in small business environments, and it is a simple product to use."
"The performance is good."
"We managed to reduce the storage space needed to 10% of the original size, without affecting data integrity, and we significantly improved the performance."
"We often use PostgreSQL for operations monitoring because we are a manufacturing company."
"The tool is user-friendly."
"The auto-tuning and NDB cluster has some limitations regarding foreign keys."
"In an upcoming release, there should be something added similar to EPL. For example, when using the flow diagram, we can create a schema. We have two useful features to add or create the table, but there should be some UI features to allow us to drag and drop to create other schemas. This would be very helpful."
"It is not as powerful as SQL Server. It can be more powerful. It is not scalable and has certain limitations, which is not the case with SQL Server."
"The licensing of the solution is on the expensive side."
"In terms of what I'd like to see in the next release, one thing that's always missing is dash boarding. There's no real BI tool for MySQL, like there is in Yellowfin and all the different tools that you get. They all have MySQL connectors, but there's no specific BI tool for MySQL. These open source projects have sprung up, but they're more general purpose."
"MySQL tutorials and guides could be improved. Often they are too complex for someone with no database experience to understand."
"If it had something similar to Microsoft’s DTS engine then it would be the best database system out there."
"There are some issues with compatibility with Java environments that need to be improved. When Oracle bought this solution there were some driver changes that caused some issues with operations."
"The solution needs to improve the query, documentation, and JSON data functionality."
"The search option is not very good."
"It still needs to be more mature and have some backup feature. We are normally dealing with Oracle's data, and we have very strong online tools to back up the data and do other things. PostgreSQL still needs to do more in this area as well as in the high availability area. There are many external tools that you can use for PostgreSQL's high availability, but there is no embedded tool within PostgreSQL for high availability. It could have a feature similar to Oracle for working on a distributed system. It can have some scripts to improve the monitoring and some tools to do performance analysis. We have a workaround for most of such requirements except for the support for a distributed system, which is very difficult to have. This area should be included in the core of the database itself."
"PostgreSQL doesn't have a feature for temporal SQL, which is useful for gathering versions of data. This feature should be included in PostgreSQL. This feature is available in MariaDB, SQL Server, Oracle Database, and DB2."
"There are several features I would like to improve that aren't working as expected. It's likely that the latest version is doing something that was missed in the previous versions. For example, the output parameters — the stored procedures — is something new in PostgreSQL that Firebird has already had for a long time."
"It is possible that in the newer version this has been addressed, but I would like the deployment in microservices architecture could be improved."
"The interface climate could be better."
"There are some products out there that have a slightly different method of implementation for the SQL language. Some of those are slightly better in some areas, and PostgreSQL is slightly better in some areas. I would probably like to match all of those products together. It is just down to the functionality. For example, Oracle has a number of options within SQL that are outside of what you would class as the SQL standard. PostgreSQL misses some of those, but PostgreSQL does other things that are better than what Oracle does. I would like to merge those two products so that there is a certain amount of functionality in a single product."
MySQL is ranked 1st in Open Source Databases with 142 reviews while PostgreSQL is ranked 2nd in Open Source Databases with 122 reviews. MySQL is rated 8.2, while PostgreSQL is rated 8.4. The top reviewer of MySQL writes "Good beginner base but it should have better support for backups". On the other hand, the top reviewer of PostgreSQL writes " Real-time data capture optimizes database performance but Views create problems". MySQL is most compared with Firebird SQL, MariaDB, Teradata, SAP HANA and SQL Server, whereas PostgreSQL is most compared with Firebird SQL, EDB Postgres Advanced Server, MariaDB, SQLite and Chroma. See our MySQL vs. PostgreSQL report.
See our list of best Open Source Databases vendors.
We monitor all Open Source Databases reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.