PostgreSQL Reviews

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. 

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.

One use case is that we installed it and built it for a customer so that he has access to the database, and he can create whatever he would like to create on it. 

We have deployed it on-premises and in the cloud.

It is easy to install and easy to manage. There is no license on it, so it is free. 

There is high compatibility with Oracle, and there are many tools for the migration of data from Oracle to Postgre. 

It still needs to be more mature and have some backup feature. We are normally dealing with Oracle's data, and we have very strong online tools to back up the data and do other things. PostgreSQL still needs to do more in this area as well as in the high availability area. There are many external tools that you can use for PostgreSQL's high availability, but there is no embedded tool within PostgreSQL for high availability.

It could have a feature similar to Oracle for working on a distributed system. It can have some scripts to improve the monitoring and some tools to do performance analysis. We have a workaround for most of such requirements except for the support for a distributed system, which is very difficult to have. This area should be included in the core of the database itself. 

I have been using this solution for almost one year.

I didn't have any issues, but I think Oracle is more stable.

I didn't have experience with that because we didn't make any changes since we built it. All I have is one server, and I can only have one standby, nothing more. 

We didn't contact them. We didn't face any serious issues that required support.

I am also using Oracle Database. The main difference is the scalability. PostgreSQL could be used for small to medium databases but not for a huge production database. I still prefer to have Oracle Database.

The initial setup was straightforward. It did not take too long. It took maybe one hour to do the installation.

It is free. There is no license on it.

Go ahead and implement it. It is a nice product, but keep a backup and try to use it for small to medium projects or companies. Some of the customers are demanding PostgreSQL nowadays, so we will keep on implementing it.

I would rate PostgreSQL an eight out of ten.

I use the solution in my company for relational data and transactional data storage as part of our microservices. We use the tool as a relational relational data storage.

The tool's most valuable feature is its simplicity. As it is SQL-based, the tool is quick to deploy and adapt. The open-source PostgreSQL tool is very useful for us. Basically, it's a simple small DB maintenance tool.

I haven't gone too deep into the tool's technical side.

I don't think PostgreSQL supports bulk databases, so it needs to have more capabilities in terms of managing the bulk data.

AI capabilities would be a good feature to be included in the tool.

I have been using PostgreSQL for five years. I am a customer and integrator of the solution.

The stable versions provided by PostgreSQL are good enough. I have not seen many features of the tool that are related to stability during my usage.

I haven't gone through the scalability aspect since I was using MySQL Server. I haven't worked to a high level in PostgreSQL, but with MySQL Server, I have managed clustering and partitioning. I think I haven't put much focus on PostgreSQL, so I am not sure how it behaves or how it works.

I haven't utilized any of the technical support, but I think it has a good online community. I rate the technical support a ten out of ten.

Positive

Microsoft SQL Server is a tool that I have used more on the on-prem deployment side. Microsoft SQL Server has more capability in terms of partitioning and scaling, but I have not tried anything similar in PostgreSQL. PostgreSQL has a good advantage when we deploy it on-premises. When it comes to the cloud, PostgreSQL is a good option because it is cheaper and can be well-managed by the cloud provider.

The product's deployment is easy.

I normally tend to go with the docker-based deployment. There are a few other options on the deployment side. We have managed PostgreSQL from Azure or AWS RDS and some other tools. I mainly focus on docker-based installation for the development side, and that is quite easy.

One person can manage the tool's deployment and configuration.

My earlier organization had paid to use the tool on Azure so that they could use it as a managed PostgreSQL tool. We had a license for the managed PostgreSQL version that is not used on the production side.

The tool is cheaply priced compared to other RDBMS providers in the market.

I haven't worked much on the tool's migration part.

I have never heard of any AI capabilities in the tool.

I rate the tool a ten 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.

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.

For us, we have the same use cases as MySQL for this product.

We've been happy with the capabilities. It doesn't have the issues that MySQL does have. 

The community support and the open-source community for it are good.

It's a stable solution.

We do find the product can scale. 

While it can scale, sometimes it requires more knowledge than SQL Server. 

They need to improve the user experience of the management. I'm not aware of Postgre needing a lot of new features, however, they can improve the user experience. That would be awesome. The backup strategies and that kind of stuff could be much better.

The solution is stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. The performance is excellent.

The solution can scale, however, you do need to be somewhat knowledgeable.

If the customer has saved a lot of money in the licensing, they may be able to afford to do the consultancy on scaling Postgre. That would help them when they scale. You can also get it on the cloud and scale with it rather easily.

There's a very strong community around the solution that you can access in order to get insights into how to work the solution and troubleshoot. 

We also have used MySQL.

The setup has a medium amount of difficulty. It's not overly difficult. 

Typically, we do implementations ourselves. That said, if it is a huge deployment or production, we might need help from a consultant or someone from the team who is an expert in the database. All in all, it's not that hard. It's not days of consultancy. It's a matter of hours or a single day.

The solution is open-source.

While you have to pay for it, for Postgre, you have to pay for consultancy and implementation. There is professional support, however, I'm not aware of the pricing for it right now. IBM maybe provides that kind of support.

We are just customers or end-users.

I'd rate the solution at a seven out of ten. It is something in the middle between MySQL and SQL Server.

We use PostgreSQL as a database, e.g. it's where we install the application. We also use it for all types of batch processing, and it also has the batch sequencing engine. We use it for everything, e.g. everything's right there in the database.

What I like most about PostgreSQL is its ease of management.

They should make PostgreSQL more secure. It's stable, but from a security point of view, it still needs improvement.

It's been a few years since I started using PostgreSQL.

PostgreSQL is a stable solution. It's also very easy to manage.

PostgreSQL is scalable.

Installing PostgreSQL was straightforward. There were just a few parameters I needed to get through, then the process became straightforward. I was able to do the installation myself.

I did the implementation of PostgreSQL myself, and did not need a vendor or technical team to help me.

PostgreSQL is for personal use, e.g. I've been using it for my applications. It's deployed on cloud.

I'm not from the core database team, so whatever features are currently provided by this solution, I'm happy with them, e.g. PostgreSQL is fulfilling my needs. Our database administrators will be able to provide more information on areas for improvement for this solution, because they know all the ins and outs of the database. I'm using this for my application, and I have not faced any issues with it.

I'm part of a global company, and in our team, we keep recommending PostgreSQL to our client, but increasing the usage of this solution depends on the client, e.g. the one who pays.

We have more than 200,000 users of PostgreSQL.

In my project, I don't need a technical team for the deployment and maintenance of this solution, e.g. I can do it myself, but for other projects, deployment and maintenance could be handled by database administrators.

On a scale from one to ten, I'll rate PostgreSQL seven out of ten.

This is an open-source solution, operates at a high speed, and supports more than one SQL language.

It integrates with different platforms, the upgrades are quite fast and the solution keeps getting better. 

This solution could be better integrated with other systems. 

I have used this solution for four years. 

This is a stable solution. 

This is a scalable solution.

We have not needed much help from the customer service team. When we have had questions, we have found the answers on Google. 

We previously used Microsoft SQL.

The initial setup is straightforward and took less than one day. 

This is an open-source solution and there is no need to pay for a license.

We recommend PostgreSQL for our customers who want an open-source solution.

I would rate this solution an eight out of ten. 

Our primary use case for PostgreSQL is data storage. 

As PostgreSQL is an open-source product, you do have to do a bit more configuration and management yourself. I would like to see it become more user-friendly. 

I do not use PostgreSQL regularly but I have been running a project that has been utilizing it for six years. I head a tight-knit group that includes a front end developer, backend developers, and hardware people. They deal with PostgreSQL and I do not have hands-on experience with this solution. 

PostgreSQL is stable and easy to use. 

It is very scalable and comes with a bonus: no licensing issues as you scale with your databases. 

Currently, 15 people use PostgreSQL at our organization. 

I am satisfied with PostgreSQL's technical support. 

The initial deployment was fine. If you read through the steps, you should be OK. 

The licensing is fine. It is not a paid database license.