TrustRadius: an HG Insights company

PostgreSQL

Score8.7 out of 10

354 Reviews and Ratings

Community insights

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.

Reviews

59 Reviews

Experiences with managed PostgreSQL Services

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

Our organization hosts a DMS system that needs a database to save configurations/passwords/etc. As we offer a cloud solution, it was clear we need a managed DB and PostgresSQL fitted that use case. Also because, instead of something self hosted, it offers a reliable managed backup, autoscaling and much more.

And of course, the Open Source aspects is a strong point, because it allows you to reduce the migration sorrows, if we would be force to switch to a different Hyper Scaler or want to use multi cloud.

Pros

  • Store data
  • Perform reasonable even with big data amounts
  • Automatically scale e.g. if switched on you can increase the disk if needed
  • Things as max connections are not restricted to be configured

Cons

  • Point in time recovery (backup) takes a long time (Sort of Hyperscaler related)
  • Not so easy to install extensions among other thins if no super user available (Hyperscaler dependant)
  • Updating from one Postgres version to another not straight forward

Likelihood to Recommend

I can only comment from the perspective of a managed PostgreSQL user. For cloud services, it is important to be cost-efficient and only pay for resources which are used. Here this solution has it strenghts, for example IBM changed its model in the past. If your application is not DB RAM/vCPU hungry the old shared plan was deprecated, so now you cannot have less than 0.5 vCPUs and 4 GB of RAM from the get-go. And even if you are not need for high availavility, two members is the minium (doubles your cost). In addition, if you work without outscaling (for whatever reason, e.g. loadtesting and the time it would take to scale is to slow) the solution might be too expensive. But I guess, when you self host, you can circumvent that.

Vetted Review
PostgreSQL
3 years of experience

PostgreSQL An Open-Source Powerhouse.

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

We are using a PostgreSQL database for multiple Java-based applications. Due to its ease of installation and maintenance, it's been our first choice. PostgreSQL database is an open source DB that has helped us in saving licensing costs. Due to its flexibility for customization, our developers can use it for specific business needs.

Pros

  • Helping us saving in IT budget as its open-source.
  • Customisation flexibility.
  • Useful in migrating legacy databases to PostgreSQL.

Cons

  • Need improvement in adding feature like zero downtime for major upgrades.
  • Too many parameters are available to set in the database, which can confuse the database engineers.
  • Frequent blocking locks occur during certain DDL operations.

Likelihood to Recommend

PostgreSQL is well-suited for applications that need to be deployed quickly and where we want to save the licensing costs. It is also suitable for applications that need unique data handling requirements, as it provides flexibility of customization. However, it's not suitable for the workloads that require horizontal scaling.
Vetted Review
PostgreSQL
2 years of experience

Useful PostgreSQL.

Rating: 8 out of 10

Use Cases and Deployment Scope

We use PostgreSQL as Storage for our BMC SaaS Solution. There are some performance challenges that we have to analyze from time to time. As we migrated from MSSQL, the used procedures differed, and we had to adapt our solution. However, we found a replacement for all our requirements.

Pros

  • Stability
  • Functionality

Cons

  • Performance problem analysis
  • Indexing

Likelihood to Recommend

I believe PostgreSQL is well-suited for any scenario where other databases, like e.g., MSSQL used. So it can be a replacement with better costs. I cannot go into deep technical details, and I'm not an administrator. however, from the user's point of view, we are satisfied.
Vetted Review
PostgreSQL
4 years of experience

PostgreSQL: reliable and cost effective.

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

The majority of our databases are built with PostgreSQL via Jupiter. Over the years PostgreSQL has been reliable and secure product. It has always provided the features that we need as a business while also allowing us to manage costs. We have been able to shift away from docker and really embrace the homebrew set up, which in turn showed its versatility and portability.

Pros

  • Built in replication gives us confidence around high availability and ease of movement.
  • Excellent introspection and tuning tools
  • Open source licensing keeps cost down

Cons

  • Horizontal write sharding becomes quite complex
  • Some queries have high latency
  • Sometimes workloads exceed and operational teams need to weigh up whats important to stay operational.

Likelihood to Recommend

I think because its well know language it allows easier introduction to new hires meaning there is less friction when a new member starts or is moved. I think too that PostgreSQL is fantastic for your basic transactional apps but when stricter standards are necessary or when relationships and joins matter it, there are better options out there.
Vetted Review
PostgreSQL
10 years of experience

PostgreSQL

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

I have worked, for 46 years, across multiple industries, charities and public sector organisations using multiple database products. One of the largest databases was recording car movements, received from a tracker every 5 seconds, we had over 2 billion rows in the biggest table and this increased for several more years after I moved on. Our working database was PostgreSQL and the operational system was Netezza, which was built on the PostgreSQL code. We used the geospatial functions to analyse car journeys.The business problems addressed by PostgreSQL include: reliability, performance, productivity, cost, scalability and interoperability across operating systems. PostgreSQL scores highly in all these areas.

Pros

  • PostgreSQL is robust and reliable. I have never known it to crash or to lose data.
  • PostgreSQL performance is amongst the best. Different benchmarks measure different capabilities, and PostgreSQL is consistently in the best performing database systems across all the benchmarks I have seen.
  • PostgreSQL has the best documentation and the most helpful error messages. This optimises productivity, by avoiding lengthy analyses to isolate any problem. (Such problems are usually wrong syntax or illogical processing requests.)
  • PostgreSQL supports some of the largest databases of structured data in the world, including the UKMet Office, National Oceanic and Atmospheric Administration (USA) and the International Space Station, WhitePages.com, OpenStreetMap and many others.
  • PostgreSQL has high conformance to the SQL standard and the relational database theory.

Cons

  • I honestly cannot think of any. I would not want it to support some of the things that are being added to other databases, such as blockchain storage.

Likelihood to Recommend

PostgreSQL is best used for structured data, and best when following relational database design principles. I would not use PostgreSQL for large unstructured data such as video, images, sound files, xml documents, web-pages, especially if these files have their own highly variable, internal structure.

PostgresSQL the definitive relational DB

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

In my team, we primarily use PostgreSQL as a relational database for standard use cases, where we for example have some information that we want to keep track of but not having everything in a single table, choosing instead to build several relations between the tables. The other use case we have, which is the primary one, is the basis for our Airflow instances - this is something set up by default by Airflow but for us it is sometimes necessary to extract information from this DB for further processing.

Pros

  • Query performance
  • Automatic upgrades
  • Retro compatibility

Cons

  • Clearer indications on what is the query plan, to optimize the query
  • More out of the box, Postgres specific, SQL functions
  • It would be nice to have a more visual aid of the relationship between all tables, but possibly this depend more on the UI used

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.
Vetted Review
PostgreSQL
5 years of experience

Best Relational and Open Source Database

Rating: 9 out of 10

Use Cases and Deployment Scope

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.

postgreSQL, a great choice from startup to enterprise

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

We use postgreSQL in instances where we need an isolated database to support a microservice architecture, or an isolated system. It allows us to leverage a simple and inexpensive database option where a larger scale enterprise configuration would be over engineering. We commonly use it for build automation systems in our organization.

Pros

  • Easy to set up
  • Simple to configure
  • Clean and effective UI

Cons

  • I would appreciate the ability to get performance tuning recommendations

Likelihood to Recommend

For a quick configuration of a database for an isolated system, PostgreSQL is a great choice. We use it as an external Database to support our build server systems. it is lightweight enough to be installed on the same system as the build server and provides a more robust storage system.
Vetted Review
PostgreSQL
3 years of experience

"PostgreSQL is the most sophisticated and adaptable database software available."

Rating: 8 out of 10

Use Cases and Deployment Scope

PostgreSQL is the most advanced and versatile DB system available and is well documented. It’s cool, and there is a lot of diversity among the people who help with it. PostgreSQL has a project (phAdmin) that allows us to carry out tasks using a friendly graphical user interface, making it an incredible database manager. It has a command-line interface for Linux and Windows that is simple to use. In addition, Golang and Python and their frameworks, such as Django for Python, can be integrated. A comprehensive documentation website makes learning about all of its features easy.

Pros

  • It works well with external data sources and runs on platforms with stable performance.
  • Clients can rest assured that their personal information will be safe and secure.
  • Many forums discuss setup and usage, and most are free.
  • Adding tooling applications to a computer is unlimited.
  • PostgreSQL runs on many OS platforms and supports ANSI SQL, stored procedures, and triggers.

Cons

  • Increasing horizontal scaling is complex, but PostgreSQL may have a solution for all replicas to accept operations.
  • No column re-ordering and better data compression are required.
  • PostgreSQL is often criticized for being slow and unsuitable for large-scale enterprise applications.

Likelihood to Recommend

PostgreSQL, unlike other databases, is user-friendly and uses an open-source database. Ideal for relational databases, they can be accessed when speed and efficiency are required. It enables high-availability and disaster recovery replication from instance to instance. PostgreSQL can store data in a JSON format, including hashes, keys, and values. Multi-platform compatibility is also a big selling point. We could, however, use all the DBMS’s cores. While it works well in fast environments, it can be problematic in slower ones or cause multiple master replication.

Don't be afraid on adopting it. PostgreSQL delivers more features than most of the paid databases from big brands.

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

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.