We performed a comparison between PostgreSQL and SQLite based on real PeerSpot user reviews.
Find out in this report how the two Open Source Databases solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The product is very similar to the SQL Server."
"PostgreSQL makes it very adaptable to several descriptions of a record. Instead of having several tables or several relations for one entity, I can adapt this entity. It can be a multiform entity. For example, here in Mexico, a company and a person can be sold to us as a physical entity or a physical person."
"PostgreSQL has complete SQL dialects and is useful for writing sophisticated and complex queries. We have experience with Oracle database. My partner is experienced in DDA and he writes sophisticated SQL queries. The solution helps to get the job done in the best possible way. In today’s age, most developers do not have strong SQL knowledge or language command. They find it difficult to write even a SQL statement. These developers write cool queries which perform badly on the database end. As DBAs, we constantly urge the developers not to write bad queries, help them learn more, and write placebo commands."
"The product is easy to use and works fast for relational databases."
"It is a pretty comprehensive database system. Its performance is good, and it does what it is supposed to do. It also integrates very well."
"The community support and the open-source community for it are good."
"It's quite scalable."
"It's a useful solution, that can be widely used."
"It was a bit easy to use compared to other tools. It's simple. I found it pretty easy to execute my SQL queries."
"The product is lightweight and highly scalable."
"SQLite’s most valuable feature is the ability to store granular-level backups of databases."
"I use Flutter Technology with the JSF plugin."
"Sometimes, you want data to persist within the app even when there's no internet connectivity. To avoid showing blank screens, we can use SQLite to store data locally and then sync it with the cloud database when connectivity is restored."
"I haven't encountered any problems in my use cases. So, it has been a stable product for me."
"Integration with other platforms could be improved."
"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."
"The scalability is limited."
"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 could improve by adding data warehousing tools."
"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."
"We have to set up event API, which takes a lot of events from the user."
"Sometimes, it becomes slow because of the network. So, there is room for improvement in performance."
"The performance could be better."
"I primarily use SQLite for small-scale applications due to its limitations in storing large amounts of data. For larger-scale projects, I typically opt for MySQL or other alternatives. Storing a large number of dates in SQLite can significantly impact its performance."
"A potential drawback is that the database file stored within the application's local storage could be accessible to users."
"There are some difficulties on the server side. When syncing data with databases like SQL Server or Oracle, SQLite requires a kind of double effort."
"Compared to other tools, the performance was less effective than that of Microsoft Access."
"It could have a user-friendly GUI and better intelligence features."
PostgreSQL is ranked 2nd in Open Source Databases with 123 reviews while SQLite is ranked 9th in Open Source Databases with 8 reviews. PostgreSQL is rated 8.4, while SQLite is rated 7.2. The top reviewer of PostgreSQL writes " Real-time data capture optimizes database performance but Views create problems". On the other hand, the top reviewer of SQLite writes " Pretty easy to execute my SQL queries but issues while uploading and importing my dataset". PostgreSQL is most compared with Firebird SQL, EDB Postgres Advanced Server, MySQL, MariaDB and OpenSearch, whereas SQLite is most compared with Firebird SQL, MariaDB, MySQL, Oracle Berkeley DB and LanceDB. See our PostgreSQL vs. SQLite 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.