PostgreSQL Reviews

We have a use case for the solution which was related to a website that we developed for a Spanish energy line transmission company. The company used to face a lot of legal issues in Brazil. We had created a SaaS product that helped them to monitor the Brazilian legal parameters. The company had used the product only for two years and then discontinued it.

The company also faced many internal problems where they had to urge the lawyers to get used to the SaaS products. The lawyers wanted to input information into another system and this is where we used PostgreSQL.

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.

I find it difficult to get connectors on the tool. For example, .NET has only one free provider in PostgreSQL. I need to pay the provider if I need something more sophisticated features. Other languages like PHP and Java have good community support. We need community support for .NET.

I would rate the solution a nine out of ten. PostgreSQL is an open-source enterprise-grade product and is available free of cost. The tool doesn’t have a big company behind it. The solution is very well documented and you can find a lot of information from the community. The solution is a good product compared to MySQL. People have been moving away from MySQL ever since it became an Oracle product.

PostgreSQL can handle heavy loads. I follow some of the most important DBA professionals in the industry and they are using this product. This tool is a rock-solid product and the most advanced relational database software that is open source.

Some open-source solutions have a restriction on the license but there are no problems when commercial applications use the solution. You cannot use a commercial product with open-source solutions that have license restrictions.

I am using PostgreSQL to develop a general ledger system. The solution is on-premise right now, but it's going to be on the cloud soon.

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.

Each of these entities has some things that are common, such as name and registration for an identity for the ISR in the US and in Mexico's it is called the SAT. We have to have different characteristics for each of them. In PostgreSQL, I can easily create a field for this moral person, with a different set of fields. It allowed me to have some plasticity on each entity that I am describing. People that are working inside the company, have some requisites that are different from one position to another. This plasticity allows me to move it for every person that is inside the company. PostgreSQL allows me to do all of this will ease. This feature is called H store, it is wonderful. 

I'm using the replication that they have inside, in case one company may wish to have the solution on-premise, they can have the replication feature that is already embedded and it's free. You don't have to pay again for that solution.

PostgreSQL could improve by providing a geographical solution for tracking trucks and people in the field. They might already have features similar to this and I have not found them. I haven't done research about this topic.

I have been using PostgreSQL for approximately six years.

The solution is stable.

PostgreSQL is scalable.

I have not used the support from PostgreSQL. I have not had any large problems.

I have found all the information I need online in many of the communities they have.

I was previously using Microsoft SQL Server and MySQL.

With MySQL, I had once a terrible problem with a group that was only giving me the first record of a group. I had to implement it through other means for the solution to give me the result that I was required.

The initial setup of PostgreSQL was very simple. I am using Ubuntu and you only have to go to the synaptic and download the package and it's already stable. It can be down in a matter of minutes, it's wonderful.

I would recommend this solution to others.

I rate PostgreSQL a ten out of ten.

We use it for inventory control.

We are able to use it on many servers and incur no cost impact, whereas Oracle charges you by the number of cores that are on each individual server, whether you use those cores or not.

The main value is that it is open source, which means it is free. Our organization has the initiative to go to open source to cut down on cost. Oracle costs us $6 million a year right now, which is killing us, and Postgres costs nothing. So, there is a big push to go to Postgres.

It is a great product, and it just works. 

They need to have a better graphical interface. There is a tool called pgAdmin 4 that they use, which is free. It is written in Java, and it is slow. They need to have a better product that is similar to Toad for Oracle, but, of course, it is hard to get something that's really great and free. Other than that, it is great.

I have been using this solution for three years.

It is better than Oracle. It is a great product.

It scales horizontally, so it is great. You can do whatever you want with it. We probably have 10,000 users. In terms of their role, they buy products, put them in the inventory, and distribute them.

It is being used quite heavily. The idea is to get rid of Oracle and replace Oracle with Postgres.

It doesn't have any support because it is open source. They provide you with the documentation that's free, and you get everything except help. You're on your own, which is okay. I and one other person came up to speed on this, and we're basically the subject matter experts (SMEs).

EnterpriseDB (EDB) is a company that provides technical support, but we decided not to do that.

We used Oracle. We're currently in the process of migrating from Oracle to Postgres, and we're doing it because of cost.

Postgres is a superior product, and it is free. Oracle's support is really terrible, so you're not really getting any support from Oracle.

It was very straightforward and easy. It is very well documented.

We can deploy a server in about three or four hours. We use a primary and a standby server, so we have two servers in the cluster.

My partner and I read the books and then just did it. I am on the development side. They get the new products in, and I and this other person evaluate them and learn them. We probably have three people in operations who are handling Postgres on the production side.

It is free. In terms of operating costs, it basically needs the same platform on which Oracle runs.

We evaluated EnterpriseDB (EDB) Postgres, which is a paid product, whereas Postgres is open source. We decided that it was better to go with a free product.

I would absolutely recommend this solution if you're concerned about cost. It seems easy and straightforward.

I would rate it a 10 out of 10. It is really great. It works amazingly well.

We deploy our databases in either a local cloud or AWS. For the locally deployed database, we have our own private cloud consisting of a couple of different data centers that we partner with. For everything else, we use Oracle or Microsoft SQL. On the Microsoft SQL side, that's not usually software as a service. It's generally done as a local installation on a virtual machine. If we're doing a deployment on an AWS environment, we use the AWS Postgres database. It's slightly different than doing the installation yourself. So if you're doing the PostgreSQL installation on a Linux environment, that's usually when we're using that directly from postgresql.org. 

It's an open-source database, so we can see the code used for that database. Also, we use it because it's lightweight, easy to deploy, and scalable for particular projects, especially if we're dealing with something that requires a Docker deployment.

I'd like to see better memory management. I think that that's one of the few areas that Postgres does not handle as well as MySQL does or did. 

I've used PostgreSQL off and on for different projects for probably about 20 years now.

Postgres' stability is wholly dependent on the skill and knowledge of the administrator who deployed it. Postgres is rock solid when deployed according to best practices as documented by the PostgreSQL community. When it's installed correctly, PostgreSQL is an enterprise-grade solution. It's reliable but requires more familiarity than you would necessarily need with a database like Oracle or Microsoft SQL out of the box.

The biggest shortcoming of Postgres and most open-source applications is support and documentation. There's usually a decent amount of technical documentation. That would be for someone that works exclusively within the database. But it would be helpful to have more documentation at the DevOps level so developers have a better idea of maintaining the database's performance without necessarily requiring a developer who specializes in that database. A lot of DevOps people are much more interested in writing their code for the databases to work. And sometimes, they end up devoting more time to database tuning than is necessary for an application developer. So documentation in that area would probably be best.

So back in late August, the developers released PostgreSQL 14, the most feature-rich deployment to date. And they did a reasonably decent write-up about the new and unique features. What I found most interesting is that you can use a straight-up Windows installer for the PostgreSQL database. And it includes all the components of the stack you need, so you don't necessarily need to know how to install its different parts. For example, suppose you're going to install it for Solaris, BSD, or Linux. So when you're installing in those three environments, it's usually packaged and requires secondary packages. And some of these packages are version dependent, so it can get complicated pretty quickly. If you are curious about how PostgreSQL databases run, I suggest you try it out on Windows first.

We use PostgreSQL alongside Microsoft and Oracle solutions. Postgre is suitable for scaling with specific projects. But while it scales very well, Postgre doesn't have the same recovery features as some larger-scale databases. For example, you can run Oracle Databases in a couple of different ways for easy recoverability should the primary database fail. First, you've got a rack for redundancy and load distribution. Second, Oracle has a feature called Data Guard that replicates the database in case it goes down. Data Guard allows you to run a completely different copy of the database that will take our main exports and keep it up to date. So if your primary database has a software or hardware failure, you can bring up the secondary database and re-task your applications to use that database. It's not as simple to do this with Postgres. 

I rate PostgreSQL eight out of 10. 

We use it in new team architectures, microservices architectures, and databases that are relatively small.

We also use it for table data, public web pages, some server applications that require data persistence, and some backend modules.

It's a useful solution, that can be widely used.

It is easy to use.

PostgreSQL has a large community.

The performance is good.

We don't have any use cases where we would use it in a large application as we do with Oracle. This is one limitation of this solution. We are unsure when it comes to deploying a large 24/7 application. 

It is possible that in the newer version this has been addressed, but I would like the deployment in microservices architecture could be improved.

I have been using PostgreSQL for five years.

We use several different versions. It is determined by the application. For server applications, we use version 9, which is an older version, and for others, we use the most recent version.

PostgreSQL is a stable solution.

This solution is used by 10 people in our company.

It is supported by a third-party company.

I have never contacted technical support.

I am also using Oracle.

I have no experience with the deployment of this solution.

The licensing model is good.

I would recommend this solution to others who are considering using it.

I would rate PostgreSQL a nine out of ten.

We use the product to manage large datasets. We also use it for forecasting. The product is integrated into our application to test the data.

The processes are quick. The data is arranged well. The tool is user-friendly. We are working on a Windows app. It is easy to view and analyze the data. The logs are valuable. The solution is reliable. It is a Windows-based application.

The search option is not very good. If I need to see data in a table, I must go into the table. The solution must provide filter options in the log files so that we can search for a particular range of data.

I have been using the product for four to five months.

We have not had any performance issues with the solution.

The solution is scalable. Though the data grows with time, the performance stays the same. Four to five people are using the solution in our organization. We are expecting an increase in the number of users soon. The data processed is large since we work on forecasting.

The initial setup was straightforward.

We do not use the product for web application development. The management decided to use the product. I recommend the tool to others. If the data format is okay, we will face no problem using the tool. Overall, I rate the solution a nine out of ten.

I use PostgreSQL on-premises to store monitoring data collected by  Zabbix Server.

I wanted a database engine that could handle an ingress of a thousand real-time values per second, delete old items without affecting performance, and handle hundreds of user queries at all times.

The solution had to support high compression and time series data while maintaining data integrity and performance.

I wanted the database engine to be easy to tune, secure, and set up.

PostgreSQL matched those requirements and has regular updates and plenty of official and community support resources.

PostgreSQL greatly improved our monitoring solutions data storage, performance, compression, and processing. Our monitoring solutions run efficiently with little maintenance.

The availability, stability, and reliability of our monitoring solutions greatly improved because the database engine scales out well, is easy to tune, easy to upgrade and manage, and supports extensions and plugins for specific use cases. One such plugin is TimescaleDB and it has proved greatly beneficial for time-series data storage and automatic partitioning of the database.The upgrade of the database has been great too, from 12 to 13 to version 14.

The most valuable feature is support for the Timescale DB extension. We managed to reduce the storage space needed to 10% of the original size, without affecting data integrity, and we significantly improved the performance.

The database engine is easy to manage, the tuning is friendly, and the integration with supported extensions is friendly too.

The database engine is free and open-source, too. Since we did everything internally, it has greatly reduced the costs of setting up our systems.

It also supports diverse kinds of replication, which is crucial for a high availability environment that we plan to set in the near future.

PostgreSQL uses high memory compared to its counterparts when a highly demanding workload with many database connections is in use, especially one that makes many concurrent connections to the database. 

Like many other databases, the tuning is manual through a configuration file. It would be useful if the database engine could detect the specifications of the machine in which it is installed and so bring some levels of auto-tuning. 

PostgreSQL replication support isn't so straightforward for multi-sources and master replicas. It will be great if native support of those replication modes become available in the future.

I have been using PostgreSQL for more than four years.

Stability-wise, I have a great impression.

It can be easily scaled.

We haven't used the official support but judging from the available resources on the website and other outlets it seems their support is good.

Positive

I used other database management systems (MySQL and its variant MariaDB) for my NMS applications before moving to PostgreSQL. I had some optimization issues on MySQL and MariaDB and decided to switch to PostgreSQL, mainly for the TimescaleDB extension support provided on PostgreSQL and which my application natively support including automatic database partitioning and compression. TimescaleDB proved to be helpful since I mostly deal with time series data and the TimescaleDB hypertables improved my applications perfomance greatly.

The initial setup was straightforward, although it needed time to get everything well-tuned. 

I implemented in-house.

The ROI is 100%.

PostgreSQL is free and open-source, so if capable admins are available then the setup cost can be negligible. We use internal resources, so it was completely free for us. One can choose the available official support too.

I evaluated other options including MySQL and its variant MariaDB & Percona Server for MySQL, Oracle DB, and SQLite.

For anybody who is considering this solution, my advice is that it is better to do enough research on the specific database engine requirements.

I highly recommend PostgreSQL with TimescaleDB extension for time-series data.

The product is easy to use and works fast for relational databases.

There could be a plugin to distribute the data on servers for the product.

We have been using PostgreSQL for one month.

I rate the platform's stability an eight out of ten. It could be better.

The product's scalability for large databases needs improvement. Like Oracle, there could be an option or solution to manage if the data exceeds.

I have used MySQL.

The initial setup process is easy. It takes about ten minutes to compete.

It is an open-source platform.

If you need a relational database, the product is a good fit. However, it is complicated to scale for large data. I rate PostgreSQL a nine out of ten.