PostgreSQL Reviews

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.

This solution is very good and efficient in joining big tables. It also provides a lot of options that, from a developer's point of view, can be utilized in a project. 

In the next release, I would like to see better integration with other platforms.

I've been using this solution for about three and a half years.

This solution is stable - I'm not aware of any performance issues.

This is a scalable solution.

The initial setup is simple - you are only required to download the installation files, which takes just a few minutes.

I would rate this solution as seven out of ten.

The solution is quite a good database for light applications for sure. This is how we are using it - as a front-end application and the canned database of PostgreSQL. The use case is comparable to Oracle, with quite a wide range of usage.

It's easy to install in Oracle and it's quite good to use for the canned database for content applications.

The solution is quite a good database.

Their pricing is very good.

The solution is very easy to use.

It's quite scalable.

The stability is good.

The installation is simple. 

I don't work with the solution often enough to really know if there are any missing elements. For me, for how I use it, it works fine.

We're only really using two to five percent of the functionality available.

While there's no perfect solution, we aren't using too much of the functionality to really be able to comment on what might be missing.

If it was free to use, it would be the perfect solution.

We're currently using the solution. We've used it at least over the past year.

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

The scalability is very good. If a company needs to expand it, it can do so with ease.

We have around 2,000 people using the solution currently. It might even be a bit more.

We also use Oracle Database. I would say the two are quite comparable.

The installation is not overly complex. You just install it and start using it. It's simple. We are using AWS for both instances so it's simple and easy. That said, I was not personally involved in the installation process.

How many people you require for the implementation depends on the implementation itself. It can be one person or it can be five. It's difficult to say. In our case, we have only one person looking after all instances.

It's not an expensive solution.

I can't recall the exact version number of the solution. We're planning to move to the latest version.

The solution is installed in the cloud, however, it's a software as a service, provided by AWS.

I'd rate the solution at an eight out of ten. It's very comparable to Oracle.

While it does depend on the use case, for the most part, I would recommend the solution to other companies and users.

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. 

We use it as an intermediary database for the collection of a variety of data points out of our data systems.

There are many departments that have different data, single points of truth. We asked them to give us different datasets, and we accumulated them in our Postgres-stored database.

It's an intermediary for a machine learning model.

I am more of a fan of doing things straight out of Python, but with the size of the data sets, we were forced to do it in SQL.

What I like is that it's quite powerful in terms of performance.

Part of the reason we use this solution is because of its simplicity and because it works. It does all of the basic things it's supposed to do and it's not anything fancy.

They are fulfilling their customer's needs. 

I had some issues when I integrated with the Jupyter Notebook. 

In the system administration, if you open the connection to the database with a notebook, there is no automatic closing of this connection. 

I would like to see seamless integration with other tools such as Jupyter Notebook. We use it with Anaconda.

Also, possibly more streamline integration with more programming languages. An API for some different languages such as MARGO and JavaScript could be interesting.

I have been using PostgreSQL for one year.

I had an issue where we couldn't find the fault, and it happened on occasion at the end of the day. Some of my basic queries would stop running. 

I had some queries run for two days and some run for a day, then I would have to try it again the next day and it would complete in 20 seconds. Sometimes, it seemed to catch itself.

I haven't had any contact with technical support from PostgresSQL. I do my research using Google.

I did not initialize this database, but from what I understand it's very basic. It was simple to do.

I would prefer programming languages to query languages. Scripting, for instance.

If you have a relational database then you want to use PostgresSQL. I would recommend this solution to others who are interested in using it.

It's suitable for everything we use. There was nothing exceptional from my perspective, but it did everything we needed it to do.

I would rate this solution an eight out of ten.

• Very good indexing solutions, especially for arrays and text search on large quantities.
• Very good behavior on large databases (>800GB) and large tables.
• Datatypes - support for vectors, XML, JSON, UUID and the functions and operators for them are very useful.
• Programming languages - I deeply appreciate the extensibility of the server to allow more than one language for scripting functions. We mostly use PL/SQL, but recently I've tried PL/v8 and was astonishing to see that it works.
• Execute with Query Parameters is a big plus for us as there are no type conversions needed to run dynamic queries reducing the run time by approximately 25%
• There is a huge amount of community interest in developing and supporting the product.

All of our BI needs are implemented using PostgreSQL functions. Our tools are designed in such a way that the BI is implemented as much as possible through our database. We need a lot of flexibility to extend the BI logic on a specific installation.

Synchronous replication is needed, and although I have only searched the web for a couple of hours the only solutions I could find were at the application level of the database.

XML and JSON manipulation functions need to be improved as for some applications we need to add new elements to these "structures". To do this with JSON I currently use a PL/v8 extension.

We have had no issues with the deployment.

There have been no performance issues.

It's been able to scale for our needs.

Try it out! Sometimes, due to the high degree of configurability and extensibility, you might see some issues arise, but it's not that difficult to figure out what's happening. You will definitely be amazed by the SQL features and extensibility.

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.

In my experience, the data quality and extensibility are valuable.

I'm a data consultant that specializes in PostgreSQL. The combination of it's open community, open source approach and it's unique features make it the perfect platform for solving today's sophisticated data challenges.

Extensibility could be even better as there are still too many things that require programming in C to add to the database. There could also be better object-oriented support. The table inheritance feature is critical to some of my work, and I wish a similar concept existed for other objects.

I've used this solution for 20 years.

There were no issues with the deployment.

I've run systems that averaged 700-800TPS (over 24 hours), with peaks approaching 10,000TPS. That was on a 4TB database.

Postgres will happily scale to very large deployments, and there are now several open source options for horizontal scaleout as well.

There is no customer support, as this is an open source/open community product. That said, the PostgreSQL community is one of the best OSS communities in existence. Questions are answered quickly and professionally. The only thing I think the community could do better is recognizing that not all users are in a position to avoid or fix data anti-patterns.

It's not the simplest database to setup, but it's also not difficult at all. The only challenge is that there are many different packages offered by different OSs i.e. Red Hat/Centos, Debian, FreeBSD, Brew, MacPorts, etc), and they all have slight differences. This can lead to some problems during install, but they're not difficult to fix.

I've used Oracle, DB2, Sybase and MSSQL. The only one that comes close to PostgreSQL is Oracle, and only because of the large set of developer tools it offers. But, it's very difficult to manage and extremely expensive.

Always hire an expert to advise you on production database deployment. Similar to security, mistakes in this area have the potential to seriously impact your business. Postgres is free, but it can be difficult to hire experienced PostgreSQL people. There is a silver lining to that, as if you can find someone with five to 10 years experience then odds are very good and very dedicated to their craft and aren't interested in just punching a clock. You can certainly find those types of people for other products, but relatively speaking they're much rarer.