TrustRadius Insights for PostgreSQL are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Reliability and Performance: Users have consistently praised PostgreSQL for its reliability and performance, with many reviewers stating that they have experienced no downtime or issues related to the database. Some users also mentioned that PostgreSQL's performance is exceptionally fast, providing them with great speed in their operations.
Ease of Use and Flexibility: Many users find PostgreSQL easy to use and appreciate the availability of good open-source tools to work with it. Reviewers have highlighted that constructing queries in PostgreSQL is straightforward and that it integrates well with all development languages, making migration easy. The flexibility of PostgreSQL's user/role management system has also been praised by users, as it allows for easy control over access to tables.
Wide Industry Adoption and Community Support: Several reviewers acknowledge that PostgreSQL has achieved wide industry adoption, making it easier to integrate into a stack and hire knowledgeable developers. The availability of a huge online community for support was highly appreciated by users. Additionally, many users mentioned the extensive documentation available for PostgreSQL, along with the ease of finding examples, which further contributes to community support.
PostgreSQL is an Open Source Database that is used for mainly Relational database Systems. We are mainly using this database because of the microservice structure. And in microservices, we have a lot of databases and also it's open source so that is good for our organization. And it's an object-relational database the performance of the database is pretty good.
Pros
Well documentation and it's free
JSON Support
It can handle large database
Real time data
Security is very good
Good Interface and easy to work
Cons
Scrolling is not good if you change something on screen you have to reset the screen
Handling JSON type is not great
data comparison is not good.
Likelihood to Recommend
Using PostgreSQL is a Very great experience it's very simple to use and PostgreSQL easily handles large datasets. and if you looking for a relational database management system PostgreSQL is great because the cost is very low compared to other databases. And the large queries speedily run and if you are stuck somewhere the documentation is great.
We use Postgres for a variety of applications, from high availability/high traffic API services to simpler CRUD style single-page applications. It fulfills a need for a low-cost relational data store that has been tested and proven to work. Its use of common SQL is known by many engineers so the learning curve is very low.
Pros
Ability to handle very large datasets, 100's of GB
Great tooling, great selection of mature tools to pick from
Available in most cloud platforms
Easy to install and maintain
Low learning curve for engineers
Cons
I don't really have any big complaints, it's popular because it's good!
Likelihood to Recommend
Postgres is well suited for a variety of applications, especially where relational data is involved. Its low cost and its widespread use makes it an ideal choice when looking for a relational database. It's fast reading and writing, so it can be used in low latency applications like APIs. It works well in CRUD style applications as well.
I would not be my 1st choice for big data applications, querying extremely large data in Postgres can be slow.
VU
Verified User
Manager in Engineering (Marketing and Advertising company, 1001-5000 employees)
Postgre[SQL] is awesome, as it ha[s] lots of distinct things in itself. It is [a] highly extensible object relation database. We are using this for our current applications like Virtual Class and StudyShot purposes. We are storing larger pools of servers for virtual class purposes, which uses Postgre[SQL] as backend server. These applications are organization-wide products. Overall, Postgre[SQL] is superb in larger queries, where it is solving our day-to-day business problems in complex programs. Its performance and security both are satisfactory. Postgre[SQL] have features to extend which is a very good [quality].
It [is] platform independent, so we need not to worry about [having a] specific environment. Very good support for replication also relieves us from [the] data lost burden. Its cost for owning and maintaining [in] comparison to SQL server is low so it [suits us well].
Pros
Built in Json support which usually takes less space and eliminates us from re-parsing again in application and can be indexed
Support for large size data is awesome. Currently for loggings of analytics data we use it
Postgre[SQL] is more secure which we have experienced. MySQL got corrupted but it retained our data.
Its extension support is awesome. Through its inbuilt concurrent, we get faster results
Cons
Its management is not easy as expected
Data compression needs to be more better
Clustering and replication need to be improved
For JSON datatype, queries need to be better
Likelihood to Recommend
Postgre[SQL] is well suited for various application and scenarios. Looking to its various distinct features, it is good for applications where a large data size is needed, and Analysis programs. In our case, we specifically utilized software for these too. Apart from this we saw that its distinct JSON support, custom data size, object oriented approach are too good.
We've used PostgreSQL for years as a tool for our data team. We use MongoDB for operational data, but we pipe MongoDB data into Postgres. If we need a chart for an investor deck or someone has a non-trivial data question, our data team queries Postgres.
Pros
BI tool integration - Periscope/Sisense, Looker, etc.
SQL is a common skill, and Postgres' dialect strikes a good balance between stability and usability
JSON support
Cons
Running PostgreSQL locally is a nightmare
Hosted solutions like Amazon RDS are hard to use
Did I mention how difficult it is to run Postgres locally?
Likelihood to Recommend
I wouldn't use Postgres for a production application, but I would recommend it if you're looking for a decent data store that anyone with SQL skills can use via BI tools.
Using PostgreSQL in all aspects of the company. Using it for our front-end platform to display data. Using PostgreSQL as part of our pipeline looking up reference data. Also using it for reporting purposes as well. The data we have is structured, but with some unstructured data, the jsonb datatype support, also helps us considerably to store dynamic data generation. Helps us scale out our platform.
Pros
Aggregation of data quickly for report generation
Lookups of reference data vs looking up in files
organization of data for quick references
quick ansi sql functions vs writing out functions in program language
Cons
regex isn't as strong
parallelization of querying of data
data distribution natural sharding
Likelihood to Recommend
Like any RDBMS, it's perfect for storing structured and sometimes non structured data in the db engine. Transactional data is perfect for PostgreSQL. OLAP data works well. What it's not suited for, is large document stores. This is where PostgreSQL doesn't do well, compared to mongo. however, newer releases show that it is getting there. Genomic data (raw data) is not suited for PostgreSQL. And PostgreSQL engine alone is not suited for timeseries data. But with extensions in place, works really well.
PostgreSQL is used across a wide number of systems. Ranging from customer-facing primary data storage of traditional relational data to using it more like a NoSQL data store with the JSON & JSONB data types. Analytical workloads in some parts of the business are serviced by PostgreSQL as well.
Pros
Permissive licensing
JSONB data types allow for migration from NoSQL data stores that haven't scaled as well as would have like when providing consistency guarantees.
Various index types to support full text search.
Extensions & customization of the database.
Geo-spatial support with routing support.
Cons
Default tuning isn't optimized for modern hardware
No native support for multi-master setups
Scaling out with partitions across multiple servers can create transaction issues in some scenarios
Likelihood to Recommend
PostgreSQL is generally well suited to basically any database workload one can think of.
JSONB data types are great for dealing with various use cases that come up to avoid an EAV pattern.
Custom data types can be supported.
Various extensions can really add a lot of excellent features.
Logical replication in later versions supports per table replication.
As a company that does a lot of consultation work in software development and database and system administrating on high levels, knowing multiple RDBMS's is essential. PostgreSQL is often required by our partners, and we use it from time to time when the business choice lands on it. Most of the time we like to work with Oracle tools, but PostgreSQL proved itself to be a viable alternative for many use cases.
Pros
Highly reliable RDBMS for free.
Has tons of features that other free solutions do not have.
Cons
In-memory mode would be useful for many cases.
Likelihood to Recommend
For smaller development projects where a reliable and free database is required, PostgreSQL is quite good. But for bigger, more robust solutions, it also stands it ground next to the "big" DBs. PostgreSQL's improvement is community based, meaning it will have all the tools and helpful features that a modern software developer needs. It's quite easy to administrate as well.
It is our primary database engine utilized in the capture, storage, and processing of all company data. We were facing massive licensing fees and large deployment times in order to deploy Microsoft SQL Server at scale. We opted instead to deploy PostgreSQL in replicated pairs (50+ and growing) in a matter of minutes! We were delighted with the ease of use and replication abilities, not to mention the amazing performance.
Pros
Transaction Speed
Customized Tuning
Cons
Active/Active High Availability
PGTune could be more extensive
Likelihood to Recommend
It is excellent when full transactional SQL is required and reducing costs is a factor. It is also excellent where replication is required.
VU
Verified User
Engineer in Engineering (Telecommunications company, 501-1000 employees)
PostgreSQL on Greenplum is being used as a data warehouse by the entire data and analytics team on my project. There are also other teams using the database as well, but it solves the business problems of running large analytics workflows with billions of rows of archived data to create reporting dashboards. It is able to run in a massively parallel processing format.
Pros
data processing
big data analytics
data aggregation
Cons
SQL syntax support
query error handling
programmatic access
Likelihood to Recommend
PostgreSQL is great as a data warehousing solution in large organizations but it is also problematic when it is improperly used as a transactional database. Postgres is a OLAP, not an OLTP database where you would use something like MySQL instead for storing live data. It has great read but poor write speeds.
VU
Verified User
Engineer in Engineering (Information Technology and Services company, 10,001+ employees)
PostgreSQL is used throughout our company to power business applications and to drive data-driven decision making. It's mostly used by software development teams as a back-end for data-driven applications. We usually deploy PostgreSQL instances via AWS and connect to them through a PaaS (Platform as a Service) that hosts our applications. Other teams use it for analytical data processing.
Pros
PostgreSQL is fully featured.
Extensible.
Has multiple schemas per database.
Provides nice SQL syntax.
Cons
Could provide better documentation of PLPGSQL functions.
Likelihood to Recommend
PostgreSQL is really good at being a data source for many applications. Because each database has the ability to have multiple schemas, a database can be separated logically according to criteria, such as which business unit the underlying data belongs to. Then, within that database, multiple schemas can be created for different purposes -- maybe one schema per application. This setup of the DBMS is great for a more monolithic data source, but not so much for a more micro-service style setup.
VU
Verified User
Engineer in Engineering (Farming company, 10,001+ employees)