PostgreSQL Reviews

The solution is primarily used to develop the databases for your application. I used it personally for a college assignment.

The solution is open-source and therefore free to use.

You can do the same actions as you can with the SQL Server.

It's a standard reliable database management system.

The solution comes with an option to work in dark mode, which I appreciate.

The interface could be much better. Maybe it took a little bit longer to understand the menu options and so on. On top of that, it's a web interface. It makes it uninteresting to look at. It's not so appealing as the options that Microsoft offers. It's a separate program that works separately and you don't mess with the browser. It works okay, you can do what you need to do, however, it's not, in my opinion, so professional-looking. That said, it's open-source so I can understand that they prefer to do it like that.

The installation process could be better organized.

The stability could be better. they release new versions all the time and they aren't quite as stable as we'd like them to be.

We've only used the solution for a few months. We used it for two projects. It was basically used across two semesters. We have used it in the past year.

The solution is not as stable in comparison to Microsoft SQL Server. I had some issues with a version, and I had to re-install it last year. Now, however, it's working fine. That said, they are always launching new updates and they seem to release them too early as they are not so stable.

I'm not sure if I will continue to use the solution. I used it for an assignment, and that's it. 

I did not contact technical support. I've never reached out to them directly. Therefore, I can't speak to how helpful or responsive they are.

I've also worked with Microsoft SQL, and I find the product to be much more stable.

The initial setup could be a bit better. They have some improvements to do especially with regards to the additional tools they propose. That part is just a little bit messy. Other than that, I thought it was very easy to install it. It's not overly complex.

I was able to handle the implementation myself. I did not need the help of a consultant or integrator. 

The solution doesn't cost anything to use. It's open-source.

I'd rate the solution at an eight out of ten. I'm mostly happy with its capabilities.

I wouldn't necessarily recommend this product for beginners. 

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.

• Integration with various programming languages
• Partial indexes
• Online backups/recovery
• Replication
• Hot standby
• Cascading replication
• Partitioning
• Performance

This is an open-source product with advanced features that support OLTP/OLAP applications with the following benefits that helps organizations grow:

• No recurring licensing cost
• Huge cost savings forever
• No vendor lock in
• One-time migration cost
• Yearly major releases
• Increase in profit margins
• Completely open source
• Community-based FREE support available
• Commercial support option

The product has room for improvement with horizontal scalability and multi-master replication options, where community work is already in progress. These features will greatly benefit customers by balancing the load between servers, resulting in great performance improvement, scalability and high availability at a fraction of the cost.

I have used it for more than 10 years.

Over the last 10 years, I have used it to handle terabytes of data supporting OLTP applications and have hardly come across any stability or scalability issues with PostgreSQL.

My company, Shreeyansh, provides high-quality, 24X7 database services along with a commercial support option. We scale our services 9/10. Customers can opt for community-based support as well.

Customers may have straightforward or complex environments. However, it's totally based on the technology in use and the amount of money spent for running their business applications.

We have special expertise in providing various database solutions to our global customers and we implement customer solutions with help of our in-house DBAs.

PostgreSQL is written in ANCI C, fulfilling all of the ACID properties other proprietary databases support. Most of the customers who use proprietary database solutions to their business applications prefer to move away from proprietary licensed databases to open-source databases to save huge amounts of recurring licensing costs resulting in huge profit margins. Customer choose PostgreSQL for its rich feature list, open source, no recurring software licensing costs, no vendor lock-in and various choices for the best commercial support and community-based support available.

I strongly recommend this product, with no recurring licensing liabilities with community support and with optional commercial support available. Shreeyansh Technologies provides various quality database services in 24X7 model to support our global customers.

PostGres is a fantastic modern RDBMS and its open nature allows you to get as low level as you need. You can define functionality, you can call from SQL and dig deep into the query planner with it's excellent explain functionality. The true open community is loaded with helpful people who believe in OSS. Every feature in PG is first, present, but secondly mature and just works. You may have bugs in your code but PGSQL will never be the cause of it.

It drives our enterprise architecture we are building.

The only thing that could potentially be improved is PGAdmin3, the DB Client that's has not been updated in quite a while. PostGres keeps ahead of the curve on it's feature set. For instance the new JSON column that's come out recently to provide nosql functionality that has been benchmarked to outperform mongo.

We had no deployment issues.

The product is quite stable, and provides awesome performance.

There's been no issues with scaling it for our needs.

It has a great support community.

I started with this product.

It's very straightforward initial configuration if you start with your distro packeges.

It's very easy, and you only need to familiarize yourself with its file structure. Sometimes you need to write your own plugin, so sometimes it is better to have it implemented by a vendor.

It's free as it's open source.

It's go good reliability and is very compliant with standards. If you are installing relational DB you likely know how to use one. If you're not familiar with RDBMS's make sure you look into and use the features of the DB like views etc. They all serve a purpose and will improve your development if leveraged properly.Huge feature set.

PostgreSQL, especially the latest versions, comes with a very rich set of server side programming tools, while providing speed, data consistency and the transaction's coherence.

This is a very wide answer, but this large environment is providing fast solutions to various needs and I see this the main power.

I have a quick example about how it reduced the amount of backend code and also improved the application's performance. When you are in a scenario where your application has an input, and based on that, you have to do several back and forth exchanges with the database to get more information or do data changes, you can do that transactionally by using a stored procedure.

Some may say that this puts logic in the database, and yes it does, but it's the most efficient way to get the right output. By exploiting the PL/PgSQL capabilities it can be done and maintained more efficiently than usual backend code.

Another reason for improvement is that PL/PgSQL is a type safe language and this reduces considerably the amount of errors and even the functional flow of the application. Stored procedures are transactional, so either everything goes well, or an error happens.

Starting with v9 it can be seen an intensive activity to bring more features, more performance or productivity. I would like to see it be more reliable, and easier if possible, to make PostgreSQL clusters - more machines working together as a single instance .Providing an autonomous solution to share data across machines or replicate when it's needed. I would like to see horizontal scaling, up and down, made easier, and if something happens (I've rarely encounter cases after version 8), easier recovery from database general failure.

I have been using PostgreSQL from v7.2 through v9.4, over more than decade. I have deployed it on both Linux and Windows machines.

My first interaction was in October 2002 and since then I've continued to use it for various applications or services, varying from a few tens of thousands of records per table to hundreds of millions and more complex deployments.

The source for Linux machines were usually ("usually" because in the beginning you had to compile certain versions yourself, especially for custom setups) the operating system's repositories and for Windows the packages prepared on the official PostgreSQL website.

I've experienced stability issues on versions 7 and 8, but setup properly none (in my case) on version 9.

Database mirroring was very impressive five to seven years ago, and since then many things have changed. At that time, horizontal scalability wasn't mature enough and we preferred to manage multiple instances independently, something that is going on today. One of my next projects is to test the limits of todays solutions for PostgreSQL clusters.

First of all I think PostgreSQL's documentation is very rich (still missing more complex examples or aspects) and provides a lot of answers. Then you may find a large community and forums. And more professional people able to help.

I've always followed this path before calling a certain customer service or support, of course with the cost of investing a lot of personal time to understand things and apply measures. But this was a personal curiosity and pleasure.

I've used a larger set of databases (including the most well-known and a few more exotic) and setups. Definitively PostgreSQL is a serious contender at the top of the list. I chose it because it's fast, reliable, rich in functionality, and it has no commercial costs for its acquisition.

Starting a simple database is straightforward, but when it comes to set up, machines for heavy duty operations, read or write, there is a consistent learning curve to take into consideration.

PostgreSQL is a complex database, but once your start mastering its features you discover that things work.

I have always implemented in-house and sometimes I've looked around for vendor sources just to understand with what they come more.

Definitiely they help reduce the learning curve and there are promises for richer scalability options.

In the cases I've seen ROI was very good and it touched visible aspects from reduced ETA of developed applications, to better performance, easier maintenance and faster support.

The investment was in proper hardware and learning curve to master the database. Charging for expertise to deploy PostgreSQL depends on the expected setup, but in all cases, my choice would be to include a database specialist as early as possible within the development team.

The reason is that pure developers tend to rely on database power, making poorly optimized queries or choosing bad structures that explode later. The data warehouse team then have to clean it up, causing a loss for everyone.

This is a very good product, and I'm very pleased, especially with the latest versions. I haven't found the perfect database yet, but definitively PostgreSQL is a candidate to consider, especially if you take into account that comes for free and is open source.

I had many debates about PostgreSQL and I've never seen yet someone getting to know it and complaining about it. It simply helps and works, but you have to be good at it. Going for commercial solutions might bring serious costs and a feeling of confidence, but this database is not only for try or start, it's reliable and well done.

We use this solution for the back-end database.

The PostgreSQL database is similar to the SQL Server but has a slightly different technology that has similar resources as well. If the customer has the confidence using SQL Server, they will be fairly comfortable using this solution.

PostgreSQL could improve by being more user-friendly. In SQL Server they have a studio where you can easily do management but not in this solution. 

I have been using PostgreSQL within the past 12 months.

I have found the solution stable.

The solution is scalable but it could improve.

We have approximately 10 users using this solution in my organization.

We are using the open-source version for eight years. We have to rely on our own skillset to manage it.

The installation is easy.

We did the implementation ourselves but it is always recommended to use an expert.

This solution can offer a cheaper choice for customers since it is open-source.

I have evaluated SQL Server.

If you have a startup company with a normal production environment then this PostgreSQL should be fine. However, if there is a professional environment where there will be some support requirements and mission-critical applications, then they should choose an alternative, such as SQL Server.

I would recommend this solution to others.

I rate PostgreSQLa seven out of ten.

I have implemented costing models. I use it to capture item costs and then do calculations to compare costs.

The built-in code procedural language is the most valuable. It has a built-in layer for code procedures. 

Its installation is very easy and quick, and it is free. It is also stable, and its performance is also good.

PostgreSQL doesn't have a feature for temporal SQL, which is useful for selecting version(s) of a row. 

Specifically the syntax 

SELECT 

FROM <table> FOR SYSTEM_TIME AS OF ...

This feature should be included in PostgreSQL. This feature is available in MariaDB, SQL Server, Oracle Database, and DB2. 

I have been using this solution for six to seven years.

It is stable.

For my use case, it was good enough. I didn't use cluster or other such things. In my previous organization, we had 10 and 20 users. In my current organization, we don't have any other users.

I haven't used the paid support. I always find information from open forums and technical guys on the web.

I was previously working in a research organization, which favored open source. I have also used Oracle, Sybase, Microsoft SQL Server, and Ingres databases.

Its installation is very easy and quick. I am running it on Linux. It took a few minutes to install it.

I do it myself. I have been doing it for a long time. For its deployment and maintenance, one DevOps person is sufficient.

It is free, but if you need support, you can go for the commercial version called EnterpriseDB. They provide paid support, and they can even do hosting for you if you want standby and support.

For our current use case, I'm evaluating PostgreSQL versus MariaDB. I am probably going to use MariaDB because I need the temporal SQL feature, which is not available in PostgreSQL.

I would 100% recommend this solution to others. I would rate PostgreSQL a nine out of ten.

It is easy grow it from a small environment to a large one.

We use PostgreSQL as the basic tool for offering our data warehouse and BI solutions. This way my customers have a free tool and I can offer a lower price for our services.

It should have a better native client tool to manage the databases.

I've been using it for nine years.

We have had no issues with the deployment.

There have been no performance issues.

It's been able to scale for our needs.

I've never used it , but this tool has a big community and they are always open to helping.

We had some problems with bigger customers using MySQL so we moved to PostgreSQL.

It's very straightforward if you are using the default configurations. It can become complex when you begin to change these configurations to adapt it to fit your environment.

In-house because we a are a technology company. I always advise to look for a consulting company, sometimes the default configuration is not enough and the tool can become a bottleneck if it isn't properly configured.

My advice is to always begin with the free licenses, and if you see that your tool is becoming a strategic solution, you can look into obtaining professional licenses.