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.
Currently, we are using PostgreSQL to support some DevOps operations, mainly related to monitoring (as a Zabbix database server) and configuration management (it is the database used by our Puppet/PuppetDB environment). We use it as a regular deployment as well as a Database as a service (on AWS RDS).
Pros
Handle large amounts of data.
It is scalable (for reading purposes).
It is compatible with so many languages as the language for triggers and stored procedures.
Cons
PostgreSQL could have a solution to accept operations on all replicas.
Could improve its "full vacuum schema" in order to be less painful for applications.
Could have an in-memory table type instead of having to create a partition on an in-memory file system.
Likelihood to Recommend
I simply can't see any reason to use another object-relational database (other than licensing of compatibility with legacy applications) instead of PostgreSQL. I can surely affirm PostgreSQL is the most powerful, scalable, and reliable open-source object-relational database ever. Being able to handle a huge amount of data safely, PostgreSQL will offer you a final result many other paid options can't.
In our department PostgreSQL is used as the main database that supports our transactional systems, reaching a consensus for the use of a single database throughout the organization requires a joint effort that leads to a feasibility study and implementation that determine the best way forward to unify the use of a single database platform.
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.
Cons
PostgreSQL installation must be homogeneous across all supported operating systems
It would be helpful to have an index of compatible tools, plugins or complementary applications within itself to increase productivity.
Regarding the administration of PostgreSQL itself, it would be very helpful to have a dashboard that will show us the insecurities of security, stability and operability in order to have an overview of PostgreSQL behavior.
Likelihood to Recommend
PostgreSQL is ideal for handling databases that contain large volumes of information due to its efficiency, speed and above all because of the good management it makes of our resources, it also behaves very well in distributed environments of high demand, if you want a database of stable data and excellent performance PostgreSQL is one of the best.
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)
PostgreSQL open source relational data management system takes on a task behind a critical and important application running in our information systems infrastructure. Although we did not like the use of a separate model database for this application because it was different and critical at first, we are very pleased at the moment, it was unnecessary to hesitate.
Pros
Offering high performance.
It's free.
It is an institutional solution. And its use in very large and important national projects.
Good at security.
Cons
No compression
No machine learning included
Likelihood to Recommend
Looking at many criteria such as the number of transactions, data type diversity, data size and application types to run in the front and concurrent use, PostgreSQL relational database is very suitable for medium and large projects. There are simpler applications for small projects.
VU
Verified User
Professional in Information Technology (Retail company, 1001-5000 employees)
PostgreSQL database is being used across the whole organization by different departments for different services/micro-services. It addresses one important business problem that is cost. We migrated from Oracle to PostgreSQL to save license cost without compromising on RDBMS requirements.
Pros
Easy to manage.
Vast number of extensions are available to meet most of the requirements.
Simple database backup and restore.
Cons
Accessing databases within the same database cluster can be done effectively instead of using dblink.
Automatic suggestion on the optimal parameters based on stats.
Likelihood to Recommend
We migrated most of the oracle databases that were used by the application services to PostgreSQL database. In most of the cases it has improved performance. From my experience, performance is good for medium to large databases but not as much different for small databases.
VU
Verified User
Administrator in Information Technology (Entertainment company, 1001-5000 employees)
The use of PostgreSQL in our organization has allowed us to scale the number of implementations without worrying about costs associated with licenses.
We use PostgreSQLl for a variety of transactional systems, from remote sites to headquarters.
It allows us to standardize configurations and implementations throughout the organization, accelerating the number of implementations.
Pros
Resilient software ensuring data integrity.
Unlimited number of installations without worrying about costs associated with licensing.
Cons
Offer a friendly alternative for configurations.
Offer health monitoring functionalities.
Likelihood to Recommend
PostgreSQL works great for transactional environments where data integrity is a priority. It also offers different types of replication between instances that can be used for high availability and disaster recovery scenarios.
It can be very complex to use in simpler environments where what is needed is speed. Or in environments where multi-master replication is required.
I've used PostgreSQL for managing the database for agriculture support system with elements of spatial analysis by PostGIS extension. This was an internal software (not intended for public markets), used by agronomists, management, and shareholders of agricultural holdings in South Russia, Volgograd region. The database includes records about crop rotations, vegetation indices, field observation data, weather data, etc. By this info, used in analytic to achieve better productivity and reduce expenses for common field works, used to grow bulk crops, such as wheat, corn, and sunflower.
Pros
Advanced spatial capabilities by using PostGIS extension
Very fast data processing and support of native ANSI SQL language syntax allows maintaining capability and scalability of database
Fast data aggregation, even by SQL or stored routines/functions
Well documented, free for use, great community. A lot of examples, and for this reason - lesser threshold for junior developers to start with
Cons
Clustering and distributed processing is difficult to use and maintain
Likelihood to Recommend
In my humble opinion, the best area to use PostgreSQL - is small and medium databases with several billion or tens of billions of records/entities with some spatial attributes analytics involved in the data processing pipeline, if needed. Using PostgreSQL with the conjunction of PostGIS extension and some other open-source software such as QuantumGIS, Leaflet, etc allows users rapidly create spatial data analytics software, maintain and modify it with few resources spend.
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)
Capital One has many LOBs (line of businesses). I have supported IAM and Commercial
LOB. They are using PostgreSQL as an OLTP database solution. Company is using Oracle, SQL Server as OLTP solution for the most of their requirements. Since everyone moving to Cloud and want to use the open-source solutions, the company encourages the IT teams to use PostgreSQL.
Pros
Open-source. No license issues like Oracle and SQL server.
Full SQL Compliance.
GIS extension for search engines or queries.
Extensions/plugins to be used for on-premises and cloud technologies.
Easy installation/configuration.
Cons
Performance optimization is needed for the database as well as SQL.
Likelihood to Recommend
PostgreSQL is best for OLTP applications and searches engines/queries. Want to save the budget? PostgreSQL is best. Want database support on On-premises and Cloud? PostgreSQL is best.
For the non-critical applications, I would recommend using PostgreSQL. For critical applications, I would recommend going through the database design, modeling, and architectural decision-making process. Proper design decisions mitigate many performance issues.