PostgreSQL vs. SQLite

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
PostgreSQL
Score 8.8 out of 10
N/A
PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.N/A
SQLite
Score 8.0 out of 10
N/A
SQLite is an in-process library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. The code for SQLite is in the public domain and is thus free for use for any purpose, commercial or private. SQLite is one of the most widely deployed databases in the world.N/A
Pricing
PostgreSQLSQLite
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
PostgreSQLSQLite
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
PostgreSQLSQLite
Considered Both Products
PostgreSQL
Chose PostgreSQL
My expirence with other solutions is very limited, but what I saw/heard is, that on Azure the managed MS SQL Server is said to be more flexible and you can use it in a serverless-ish fashion. But on the other hand, PostgresSQL is still strong regarding its efficiency. And in my …
Chose PostgreSQL
Being open source, PostgreSQL offers the highest performance among its peers. It has a strong support community where we can find solutions to most of the queries. It's suited for GIS (Geospatial) based applications, making it unique from its peers. There are fewer databases …
Chose PostgreSQL
We had to use PostgreSQL as that is the DB preferred by our SaaS Provider.
Chose PostgreSQL
PostgreSQL holds it own against both these options. Some of these DBs are in play for certain needs but the majority are PostgreSQL because of cost and operational performance.
Chose PostgreSQL
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
Chose PostgreSQL
MySQL is an Oracle product which has in itself some known issues due to that (support, contract terms). Based on my knowledge, PostgreSQL support everything that MySQL support (syntax wise) and it adds more improvements and syntaxes that make the life of database engineers and …
Chose PostgreSQL
First It's open source and it's cost-effective compared to other databases.PostgreSQL can be easily integrated with numerous platforms. It is well known and appreciated so relying on it as our system database can be easily accepted by our customers. And if your developing a …
Chose PostgreSQL
For our use cases, PostgreSQL is just as feature rich as other options, costs less, and is simple to get up and running. There is also a plethora of documentation to support it which makes it a great option for a small scale startup without needing high levels of expertise to …
Chose PostgreSQL
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage …
Chose PostgreSQL
I've been using different databases for the past 20 years, solutions like MS SQL Server, MySQL, MariaDB, Interbase, Firebird, DB2, etc., and by using them I wasn't able to be neither close to the performance PostgreSQL deliver. Also, it is one of the most popular databases on …
Chose PostgreSQL
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same …
Chose PostgreSQL
We evaluated both PostgreSQL and MySQL, two popular open source relational databases. While they are very similar in most areas, PostgreSQL's reliability and performance won us over, plus it has much better support from cloud vendors we also work with.
Chose PostgreSQL
Postgres stacks up just [fine] along the other big players in the RDBMS world. It's very popular for a reason. It's very close to mySQL in terms of cost and features - I'd pick either solution and be just as happy. Compared to Oracle it is a MUCH cheaper solution that is just …
Chose PostgreSQL
A free corporate professional product. Who does not want to have such a thing, we hesitated because we did not know the product before and frankly we did not want it at first. But when we give it a chance, it has been running smoothly for years.
Chose PostgreSQL
When we were originally evaluating Redshift we ran into some issue with dates. Either way, Postgres is a better choice than Redshift because it avoids vendor lockin. We ended up choosing Postgres over MySQL because it was easier at the time to get a hosted Postgres cluster up …
Chose PostgreSQL
As I have been telling all along, PostgreSQL is much cheaper compared to the other RDBMS solutions. It has got better performance with some of the application services that we are using and is easy to maintain. Overall, we are satisfied migrating to PostgreSQL database clusters.
Chose PostgreSQL
Much more mature and stable when compared to MySQL with features such as MVCC, complex subquery plans, ORDBMS, and NoSQL support. With Oracle retaining rights to MySQL its future as an open database is less secure and is no longer in the hands of the community. PostgreSQL also …
Chose PostgreSQL
Its main characteristic is the integrity of the data. In addition, being free software, it has no costs associated with its license, which allows the number of installations to be scaled without problems.
The technical staff quickly learns about its installation, configuration …
Chose PostgreSQL
Both Oracle and MS-SQL database option fell when we evaluated the effect on our overall solution cost to our customers. customer examine the overall cost of the solution they buy, selecting Oracle or MS-SQL would leave less money in our pockets.
We are Linux based solutions and …
Chose PostgreSQL
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale.
SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows …
Chose PostgreSQL
We selected PostgreSQL due to the number of employees who have used it in the past.
The data consistency guarantees.
The multiple transaction isolation levels support.
Chose PostgreSQL
PostgreSQL outperforms every other option. It is faster, more flexible, more reliable, easier to maintain, and more consistent in behaviour than any of the other offerings.
Chose PostgreSQL
The main reason for select PostgreSQL against MS SQL Server Express edition is the necessity to use open-source platform, without any issues for licensing, client licensing, etc. etc, which is usually follows developers and project managers when they start to use products and …
Chose PostgreSQL
I think Postgres stacks up great against all modern database solutions and has continued to be a trend leader in this space.
SQLite
Chose SQLite
Postgresql is more advanced features then sqlite, however it needs a server and complexity is high for low level development work. for offline work sqlite is best. duckdb is great for analytics , it is the data base for analytics and better then sqlite for analytical purpose. …
Chose SQLite
In a mobile project it is easier to use, but on desktop, Firebird might be the better choice and it also has an embedded version.
Chose SQLite
I also use other Database Systems, but for small apps with offline storage, SQLite is a good and easy to use Database.
Chose SQLite
SQLite is faster and also Light weight as compared to Microsoft SQL Server. Also being open source it reduces the application development cost drastically
Chose SQLite
SQLite has CRUD queries and manipulates external files. Cross-platform support includes iOS, Android, Mac OS X, and Windows. Compared to other databases, it is fast and straightforward to implement. Even if an application crashes, there is no effect on the database or the data …
Chose SQLite
We looked at other traditional RDBMS products, but found them to be cumbersome to deploy. They take up more space, and consume more computing resources than SQLite does. While the performance or direct integration to our primary applications may have been better or easier if we …
Chose SQLite
SQLite has many types of queries to do CRUD operations. and even do manipulation to external files as well. it is fast and easy to implement compared to other Databases.
SQLite support atomic behaviours, so app crash in any situation, the won't impact database or data within …
Chose SQLite
Microsoft SQLExpress: More heavyweight, not as lean in terms of disk space or processing requirements. Involves Microsoft's tentacles to be involved.
Chose SQLite
SQLite is considered better against these two depending on the needs and phase of the project. If we require a lightweight yet reliable database which should also be portable across different platforms and speed is the most important part of the query and data security is not …
Chose SQLite
I think there is no real competition between them.
In "SQLite" you can hear "light" when you don't need to store a big amount of data and when you need something easy to deploy, SQLite is a good choice, I didn't find those qualities in other database systems I knew.
Chose SQLite
When looking at the original items available, Valentina was a serious contender. What was good about SQLite was the familiar SQL interface and way it accessed data. Valentina, at the time, had issues with index corruption requiring vigilance with the database maintenance making …
Chose SQLite
SQLite stacks quite well against Microsoft SQL server management studio however we need the Microsoft security for our data MDSN documentation is poor but available.
Best Alternatives
PostgreSQLSQLite
Small Businesses
InfluxDB
InfluxDB
Score 9.0 out of 10
InfluxDB
InfluxDB
Score 9.0 out of 10
Medium-sized Companies
SQLite
SQLite
Score 8.0 out of 10
Neo4j
Neo4j
Score 9.0 out of 10
Enterprises
SQLite
SQLite
Score 8.0 out of 10
Neo4j
Neo4j
Score 9.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
PostgreSQLSQLite
Likelihood to Recommend
8.3
(0 ratings)
8.0
(0 ratings)
Likelihood to Renew
9.0
(0 ratings)
-
(0 ratings)
Usability
8.3
(0 ratings)
8.0
(0 ratings)
Availability
9.0
(0 ratings)
-
(0 ratings)
Performance
7.0
(0 ratings)
-
(0 ratings)
Support Rating
9.3
(0 ratings)
1.0
(0 ratings)
Implementation Rating
9.0
(0 ratings)
-
(0 ratings)
Configurability
-
(0 ratings)
10.0
(0 ratings)
Ease of integration
-
(0 ratings)
10.0
(0 ratings)
Product Scalability
8.0
(0 ratings)
-
(0 ratings)
User Testimonials
PostgreSQLSQLite
Likelihood to Recommend
Based on my experience, PostgreSQL is exactly what I imagine when thinking of a relational database: it is fast for querying and intuitive (if the underlying relations have been well written) and its writes are also efficient. Of course you need to know that a relational database is what you need, for example I would not recommend it if you have a lot of unstructured data that have no way to create a relation from and if you need to run heavy aggregations over your data, as it is not where PostgreSQL would shine.
Read full review
The portability and ease of use has us doing local development, and then shipping the database to production for implementation. This compact deliverable object is great. Until multiple developers need to access it at a time. It is a caveat, but we create a database per integration as it is easier to manage. Using a SQLite database to manage more than one integration or task is not something we would recommend.
Read full review
Pros
  • The stability it offers, its speed of response and its resource management is excellent even in complex database environments and with low-resource machines.
  • The large amount of resources it has in addition to the many own and third-party tools that are compatible that make productivity greatly increase.
  • The adaptability in various environments, whether distributed or not, [is a] complete set of configuration options which allows to greatly customize the work configuration according to the needs that are required.
  • The excellent handling of referential and transactional integrity, its internal security scheme, the ease with which we can create backups are some of the strengths that can be mentioned.
Read full review
  • Our products are using SQLite in embedded Linux and in Windows software.
  • It is truly a stable cross-platform database.
  • The fact that it is a zero-configuration database engine, it is particularly a nice advantage when you work in the embedded world.
  • Being a single database file, it provides ease for those who need to quickly transfer data to someone else, or quickly browse data.
Read full review
Cons
  • The query syntax for JSON fields is unwieldy when you start getting into complex queries with many joins.
  • I wish there was a distinction (a flag) you could set for automated scripts vs working in the psql CLI, which would provide an 'Are you sure you want to do X?' type prompt if your query is likely to affect more than a certain number of rows. Especially on updates/deletes. Setting the flag in the headless(scripted) flow would disable the prompt.
  • Better documentation around JSON and Array aggregation, with more examples of how the data is transformed.
Read full review
  • Although it is excellent at what it does, you should be really careful and plan accordingly if you know that your database is going to scale at a huge level because it is not suitable of databases which are of Enterprise level and demands top-notch security and protection.
  • If your project involves multiple people working on the same database simultaneously, then that becomes a big problem, because it only allows single write at one time. You really need to be forward thinking in a manner to predict if this database will cater to all the needs of your project.
  • The most common difficulty with this is the lack of some of the basic functionality which is present in the other premier databases like Joints, Stored Procedure calls, Security and permission grants. If you do require all those things then you are better off not using this software.
  • Lastly, if you are using this in an Andriod App development cycle then also your options are limited because it does not integrate with PostgreSQL and MYSQL.
Read full review
Likelihood to Renew
As a needed software for day to day development activities
Read full review
No answers on this topic
Usability
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
Read full review
I have given this rating cause its irreplaceable in some of the areas like no more installation need except from a single library. I find dialect is simple in use cases. its suitable for any professionals with various skill levels. its easily connect with various os and devices. very less maintenance or administration required.
Read full review
Reliability and Availability
PostgreSQL's availability is top notch. Apart from connection time-out for an idle user, the database is super reliable.
Read full review
No answers on this topic
Performance
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
Read full review
No answers on this topic
Support Rating
There are several companies that you can contract for technical support, like EnterpriseDB or Percona, both first level in expertise and commitment to the software.
But we do not have contracts with them, we have done all the way from googling to forums, and never have a problem that we cannot resolve or pass around. And for dozens of projects and more than 15 years now.
Read full review
I haven't needed support yet.
Read full review
Online Training
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
Read full review
No answers on this topic
Implementation Rating
The online documentation of the PostgreSQL product is elaborate and takes users step by step.
Read full review
No answers on this topic
Alternatives Considered
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
Read full review
SQLite has CRUD queries and manipulates external files. Cross-platform support includes iOS, Android, Mac OS X, and Windows. Compared to other databases, it is fast and straightforward to implement. Even if an application crashes, there is no effect on the database or the data it contains. The user interface is best for input and output. It's best for developing skills and project deliverables.
Read full review
Scalability
The DB is reliable, scalable, easy to use and resolves most DB needs
Read full review
No answers on this topic
Return on Investment
  • A robust and reliable platform reduces the risk of data loss and confusion.
  • Using an almost free product is economical. No license fees = minimal ownership cost.
  • Efficiency is high due to quickness and excellent resource management.
  • PostgreSQL helps us achieve our goals, and there are no time-consuming management tasks.
Read full review
  • No licensing fees has a net increase on ROI
  • The active community has kept support costs low, further increasing ROI
  • The wide range of supported platforms and high level of compatibility has increased ROI by reducing time spent porting the database model to any platform specific solutions.
Read full review
ScreenShots