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.

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.

The database for the accounting systems is our primary use case for this solution. Business software is 80% of my use case in the accounting software. It's a good tool for planning. I work with financial data and the data mining aspect is very important, as I need to access the data easily. The data is the most important thing. Sometimes the software developers forget this part because they just want to save the data on the database, but they don't know how to manipulate the data. The performance of the solution is dependant on how easily and quickly you can obtain access to the data.

I can use Unity Kinematic. It's not easy but you can create a multi-tenant database in Postgres and I think it's a must-have in software development. With the database, you can provide a multi-component at the same service with the same performance, scalability, or all those things. 

PostgreSQL is limited to 32 TB in maximum table size for version 9.6 and earlier. This can be problematic for large databases. We currently don't have the multi-tenant feature and we require that with the contract integrated reassurance. To create have one tenant or more tenants, I need to implement or develop a software solution to connect with the multi-tenant, and to connect each tenant. PostgreSQL is not great for software developers, but it is adequate. For developers, databases such as Firebase and MongoDB technology are better. With PostgreSQL, all you need the database for is to save your data. This function on its own is not enough. The database and applications can become very slow. To debug you need to make the database query display information on your device. Some developers are not experienced in developing databases. This is especially difficult for junior software developers, and they often need more experience to be able to deal with that aspect.

We have been using Postgres for about 10 years. 

It is a stable database.

Because PostgreSQL is limited in regards to the amount of data it can hold in a single table, you often think it might be better to change the technology. Other than that, it is a good solution for business.

Sometimes it is not simple to resolve issues, but the PostgreSQL community sometimes helps to find answers to questions.

I think it is difficult to setup. I amended my ID and Oracle advised me to change it, for it to work.

If you want one tenant, you can use MySQL. If you want a multi-tenant, I think Postgres is better. SQL on PostgreSQL is linked to Oracle. Oracle and Postgres is the same thing, the same language. You will not have a big change for the software developers to migrate from Oracle to Postgres. 

I would rate PostgreSQL 8 out of 10. 

It is a backend database for security. We dump the data, collect the database, and then analyze it using some BI tools.

The system can perform faster analysis by providing it with a lot of memory. Speed is crucial for analytics. Currently, the main reason we haven't adopted Elasticsearch is that we lack the necessary expertise to manage it.

Postgres should focus on building a stronger knowledge base. They also need to expand their integration capabilities, so more tools and resources are available to manage it. But it is more secure than MySQL.

I have been using PostgreSQL for three years.

We are a team of about 32 people, three of them are focused on software development and installations. We also collaborate with a software company that handles the software development. We then present it to the customer. Our work is primarily focused on security.

Some applications focus on MySQL, while others use Postgres. MySQL to be more is versatile. MySQL seems to have more users, tools, and applications deployed on it, which is why many people default to it over Postgres.

MySQL may have an advantage because it supports more applications and has broader compatibility.

The tool is very easy to deploy and manage. It takes one or two days to complete.

The tool is free of cost. For now, it's not about making money. But once we perfect it, we can offer it to customers willing to pay for support and other services. Most of my deployments are free.

We are primarily a service provider rather than a software developer, though we do have teams experienced in software development. We collaborate with an external provider to develop security and cybersecurity software.

Overall, I rate the solution a seven 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.

We are using it as a database to store information.

Postgres SQL is quite a good database.

The performance is good.

I have noticed that user and access management should be improved. Connection pooling should be improved. We rely on connection pooling.

Monitoring is incompatible. It is open source. To advance, you must access the internet and download and test various other tools, or develop your own tools. With Microsoft server, it is one single platform that provides you with everything, but with Postgre you have to install or check different tools to integrate with it. That's the annoyance, but it's still the way open source technology works.

I would like to see better management in PostgreSQL.

PostgreSQL is easy to scale.

We have a medium-sized company.

We don't have technical support. It is community-based. We get assistance through Github.

We have been working with Microsoft SQL.

The main difference between SQL and Postgre is that Postgre is open source. It's completely free.

It's very simple to set up.

Postgre is open source. It is almost completely free.

The community version of Postgre is basically free.

We are utilizing the database's active native security features. As a result, we currently have no need for any external security tools. We had, but we worked around it.

The advice would be to go with a managed Postgre. If you're going to install Postgre in the cloud, for example, it's better to go with a managed Postgre rather than handling everything on our own.

I would rate PostgreSQL a nine out of ten.

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.

Currently, I'm doing a lot of source applications with Ruby on Rails, React, and mobile applications. PostgreSQL is my preferred database over MySQL. It's open-source and licenses are free, so it is excellent. The SQL queries are almost the same as MySQL.

Clustering is the number one feature. It is also open-source so it is free. It can also be clustered, to allow fault tolerance. MySQL has to be licensed, but PostgreSQL does all the same things. I have deployed both. You benefit from the way you use it. 

It could be improved by using parallelization. We want distributed computing. Some databases handle huge volumes of data better, such as the NoSQL database, MongoDB which can handle 100 000, or a million people using the same data search. PostgreSQL is going to take longer to do this, but it is more structured, and unlike MongoDB data is less likely to be duplicated. Large volumes of data can be handled better in PostgreSQL if the queries are written well.

I have been using PostgreSQL for about 2 years. I used to use version 9, about two years ago but right now I'm using version 10 or 12. I know how to create database functions. I know how to create relationships between data like primary keys and foreign keys etc.

I think PostgreSQL is more stable than MySQL.

As an RDBMS, a relational database management system, it scales well.

I have mainly used the Stack Overflow site for support, which is not technical support in particular. I have never been in a situation whereby I'm stuck and I have to go and ask PostgreSQL support.

The difficulty of the initial setup depends on the application you are deploying the code to. It can be integrated with Docker to enable automation of this process. I put PostgreSQL in a Docker container and then I just collect it. It just works wherever I deploy it. It takes less than three minutes. I use a continuous integration process. The Docker orchestration engine such as Kubernetes or Docker Swarm can be used to integrate with it. I store the code in GitHub or GitLab and your code is always there. Depending on the technology you're using, some things change in your configuration.

I have deployed them to Oracle recently. I've also deployed it in the cloud. There's really nothing special about the cloud, as long as I use the PostgreSQL machine I can deploy it anywhere. I want to deploy it on the Google cloud platform, and Amazon Web Services as these are well known virtual machines.

When it comes to pros, I would put MySQL and PostgreSQL in the same class. let's say I'm trying to write to the database and then the power went off. It will still keep the data integral. I don't have duplicated data, and data integrity is intact. With NoSQL databases I have to duplicate queries in case something like this happens I don't know whether my data is going to be integral in cases like a failure situation. PostgreSQL has the rollback function which remains integral. I cannot build a search engine using PostgreSQL, because that would be a very expensive hit on resources. Alternatively, with the ElasticSearch utility, and the use of load balancing, it is very easy to use. Elasticsearch returns substantial results and works in the background. I cannot do that with MySQL or PostgreSQL databases as that's actually a very expensive use of resources.

My advice would be to use PostgreSQL instead of MySQL because of licensing issues. Another reason is that Oracle may remove MySQL soon or add substantial costs to using it It may even turn into something like MariaDB, and then you would need to know if MariaDB and MySQL work the same? PostgreSQL really works well. There are a lot of other databases around right now, but PostgreSQL is the most popular. It is not like a hammer and a nail situation whereby it is the only thing you have to use. If you need a relational database management system, go for PostgreSQL instead of MariaDB or MySQL, then use it side to side. Can also consider other engines out there, like other NoSQL engines, perhaps. 

I would give it an 8 out of 10. PostgreSQL is not suitable for all types of applications, hence why I gave it an 8 instead of a 10.