PostgreSQL Reviews

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 often use PostgreSQL for operations monitoring because we are a manufacturing company.

We often find the solution's datetime datatype challenging.

I have been using PostgreSQL for four years and five months.

PostgreSQL is a stable solution, and we haven’t faced any performance issues.

We faced no difficulty in installing PostgreSQL.

It took us five minutes to deploy the solution.

Overall, I rate PostgreSQL an eight 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 as a backend for some vendor-supplied tools and products. We also do a certain amount of software development, and we use it as the database platform behind our own software.

We have a number of deployments, and the version number very much depends on the vendor software requirements. We have on-premises and cloud deployments.

It is a pretty comprehensive database system. Its performance is good, and it does what it is supposed to do. It also integrates very well.

There are some products out there that have a slightly different method of implementation for the SQL language. Some of those are slightly better in some areas, and PostgreSQL is slightly better in some areas. I would probably like to match all of those products together. It is just down to the functionality. For example, Oracle has a number of options within SQL that are outside of what you would class as the SQL standard. PostgreSQL misses some of those, but PostgreSQL does other things that are better than what Oracle does. I would like to merge those two products so that there is a certain amount of functionality in a single product.

We have been using it probably for two years.

In terms of the number of users, the users on PostgreSQL itself are probably application-level users, so you may only find two or three accounts per instance, but the application-level users can easily go up to 300.

We use the open-source product. We don't take it from any given supplier. So, we haven't got any tech support.

The tech support primarily is me. I am a systems administrator, and I do database administration as well. If we need any further in-depth support, depending on which product is sitting on top of that database, we will go to the vendor, but like most IT teams, we would admit that Google is your best friend.

We were using Sybase. We've actually transitioned most of it over to PostgreSQL.

It is easy to install. The deployment duration depends on what you're deploying. If you just want a database, I can have a PostgreSQL database installed and deployed in probably about 20 minutes. If you're looking for clustering or failover and mirroring, that would obviously impact the time, but it doesn't take a significant amount of time.

I deploy it myself.

It is open source. There is no licensing.

It is a very good RDBMS, and I'm quite happy with it. It does what it says, and it does it fairly well. I've seen some bits that are stronger in other products and some bits that are weaker in other products. My recommendation would depend on the requirements and the use cases.

I would rate PostgreSQL a nine out of 10. It does its job adequately, and I am quite happy with what it does at the moment. You wouldn't hear a 10 from me for any database vendor at the moment.

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.

• 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.

• Free and open-source RDBMS, with a permissive license
• ACID compliance
• Multi-version concurrency control
• Custom data types
• Array data types
• PL/Python stored procedures

Back in the day, MySQL had storage problems with InnoDB (everything in a single file), and we wanted ACID compliance. So we decided to use PostgreSQL for that, and it helped us achieve that goal. PostgreSQL's feature set was excellent for our needs, and we didn't want an expensive (meaning hardware utilization) RDBMS. Fit like a glove.

There's always room for improvement. Better SELECT performance is something that PostgreSQL could really benefit from. Replication should also be made easier. PostgreSQL also lacks a good tool like MySQL Workbench. PgAdmin3 works, but it's funky and crashes sometimes.

We've been using PostgreSQL in production since version 8.4, in 2010.

I have not encountered any deployment, stability or scalability issues. It's been running since version 8.4, updating one version at a time (9.0, then 9.1 until 9.4). Database is currently at 6GB, works without a hitch.

I have never used or never needed technical support. StackOverflow covered all our needs on this scenario.

Up to that point, we used MySQL. The decision to change came with a new version being written from scratch, and PostgreSQL being better suited for our needs.

The initial setup was somewhat complex. We had to import the old database, which was in MySQL. Most tables were rewritten, and the team was not used to PostgreSQL at that time, so there was a small cultural impact.

Implementation was completely in-house. On our case, it was much better to train the team to use a new RDBMS than to use external consultant; after all, our team is a development team.

Since it's completely free, the ROI means only the time spent by the team to get the database up and running, and the time maintaining it. I'd say it doesn't compare with any other solution I've worked with before.

PostgreSQL has extensive and comprehensive documentation. Chances are that you'll find your answers there for 99% of the cases. For those answers you don't find, you can always go to StackOverflow. If you're not a DBA or a programmer, I'd suggest hiring external help, as with all the cases with databases (RDBMS or not).

Strong enforcement of data types, because it can catch many errors and mistakes and protects data. Standard conformance, because in the end you are not locked to single vendor.

We used MySQL for many tasks, because there were simply more documentation available, but while using it, we found many serious weaknesses with it like no data validation even for string length, no transactions, etc. PostgreSQL catches a lot of things that MySQL didn't because it is serious about the data it protects!

It needs more parallelism for big tables. This is already in PostgreSQL 9.6 beta so things are looking promising.

We've been using it in production since 1999.

We have had no major issues with the deployment, but tweaking does need to be done.

There have been no performance issues.

It's been able to scale for our needs.

Excellent mailing lists with active developers. Once I sent them my query which was about slow performance due to double sorting (group by, order by), and the fix for it went into PostgreSQL 7.4, because Tom Lane noticed that in such cases PostgreSQL should not do two sorts. So after upgrading to 7.4 things got way faster without touching the code at all.

We previously used MySQL. PostgreSQL tries to solve things in the correct way for all platforms, all file systems, and all users. In the end, this means you get a better working and more stable system. They try to stay away from hacks and other non-portable or limited solutions and prefer to work inside the system. For example, an operating system already does many optimizations so why would one want to reinvent things with raw file systems, etc. like Oracle tried to do in the past?

Defaults for PostgreSQL are very low. In almost all situations one has to do some tweaking to make it perform better. It does not take much time to do it at first, but has to be done!

I did it myself with help from the internet. For beginners, I would advise you to read the documentation that is available. Also, you should read some books such as "PostgreSQL: Up and Running, 2nd Edition". "PostgreSQL Administration Essentials", "PostgreSQL 9 Administration Cookbook, 2nd Edition". Alternatively, you could look into getting professional help if you are in hurry.

Explore this new world. PostgreSQL has taken a quantum leap over the last 20 years, and now it seriously threatens more established database vendors.