PostgreSQL Reviews

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. 

In my experience, the most valuable features of PostgreSQL are streaming replication, rich indexes support, extensibility and NoSQL features such as hstore and JSONB. This features are very mature and stable, we use them in many projects, they're predictable, always work as expected and without problems.

In future releases I would like to see built-in realization of multi-master cluster with sharding, effective partitioning, incremental backup, optimizations for SSD, connection pool facilities, and built-in replication for tables and databases.

I've used this solution for five years.

There are no issues with deployment. Postgres has a very verbose and clear documentation and install instructions.

From a scalability point of view, there are no difficulties. It works out-of-box without any third party tools, but streaming replication allows you to scale read-only workloads. For write scalability, Postgres-XC or Postgres-XL should be used.

I don't use any services and technical support, and th community's support is very helpful, friendly and the members have rich experience with PostgreSQL.

I don't use any similar solutions such as Microsoft SQL, Oracle, or MySQL.

The initial setup is simple and doesn't take a long time, but in serious projects, PostgreSQL requires additional configuration optimizations as do the other RDBMS.

We did it all in-house. You should read all the official documentation as all the answers are there.

PostgreSQL is an amazing product, very stable, predictable and reliable with rich set of features.

Common Table Expressions(CTEs). It's powerfull, easy to write and read and very flexible.

JSONB (Binary JSON storage), because I can have both relational and non-relation data storage at the same time with this data type. In addition, by using Generalized Inverted Indexes (GIN) it supports fast lookups and simple expression search queries.

Replication is not yet as well implemented as in MySQL.

I've been using it for one year and five months

There are some issues around different OS, but not a big problem.

There are some issues around different OS, but not a big problem.

There are some issues around different OS, but not a big problem.

The documentation could be written better, but there is a huge community committed to help.

I used MySQL, but for safety and consistency issues, I moved to PostgreSQL

Straightforward, easy and intuitive.

In a vendor team, we develop products for different segments stores. In the implementation, keep in mind the configurations and platforms that are available, it certainly will save time and avoid potential problems.

Currently this is one of the best solutions on the market. It is a tool without cost, powerful, easy to learn and with a large active community.

It is an open source solution and that is a database engine very powerful. Besides it is highly configurable. I prefer PostgreSQL over MySQL or MariaDB because you can create several databases with many schemas and create roles like owners, and not only grants over tables, or procedures. On the other hand its very easy and intuitive to administrate the connections by hosts, databases, and roles.

PostgreSQL is a powerful dateserver although not like Oracle. So we can make many developments in a cheaper way with high availability. Besides, its very useful tool for debugging with a soft learning curve.

It needs to be able to cluster. We have implemented the high availability with a master-slave mode and one host in only read mode. This is the worst feature of this product and the quality sign of Oracle.

I have been using PostgreSQL server for three years.

The upgrade from v8.4 to v9.3 was a little hard, but this was executed finally well.

We had no issues with the stability.

We've had no issues with scaling it for our needs.

I've not had to contact them.

I use MySQL, MariaDB, and Oracle. I chose PostgreSQL or others depending of the project. For Java implementations I prefer PostgreSQL, and for PHP development, I prefer MySQL or MariaDB,

In my opinion the initial setup is easier than MySQL because it is more intuitive, but you must to edit a couple of config files, and become more aware of the entire infrastructure.

It's open source code, so you get it for free and need to contribute to debugging errors and improving the code.

Be patient! Like most open source tools, this requires commitment and a little knowledge.

* pg_hba.conf

* A fragment from postgresql.conf

* How to access to database-server using psql client, and create a database

Create a user/role and be owner for a database. We can list all databases with "\l".

We use it to convert the databases. We also use it to make a request from my PMS with the Oracle-based server through the third-party interface.

We use this solution for the interface between our property management system and the cloud-based system. It works from both sides.

It is very simple to manage.

It is easy to use.

My main concern is that I can use it to connect with the interface. It is simple, it's good.

It needs more integration.

I have been using this solution for two years.

I have not explored the scalability of this solution yet.

I will continue to use this solution but I don't have any plans to increase our usage.

I have not contacted technical support.

The initial setup is straightforward. It was easy to install.

It took only one day to install, and two to three days to connect with the database.

We have a team of three, two admins, and one engineer to maintain the solution.

We had help from a company from Norway, one from South Africa, and one other from Dubai.

We do not pay for licensing.

Depending on the type of work the user wants to do with the interface I would recommend this solution or not.

I would rate PostgreSQL a five out of ten.

Overall it is an excellent RDBMS and it is easy to use and administer. In PostgreSQL 9.5 the table inherent Foreign Data Wrappers(FDW) is available. This extension is available for most databases which makes building server federation very possible.

In 9.5 support for FDW was improved which means it is now possible to import a complete foreign schema. Foreign Table inheritance is now supported as well. They have also improved the Foreign Query optimization since v9.4. Lastly, It has low maintenance requirements so not much has to be done as far as DBA tasks go.

We were able to use the latest features described above to facilitate the integration of disperate data sources into our Postgres Data Warehouse.

• Improved support for parallel query execution
• Merge Joins
• Improved Handling of Materialized Views

I've been using it for years.

We have had no issues with the deployment.

There have been no performance issues. It's a very stable environment.

It's been able to scale for our needs and easy to extend when needed.

Although there is no tech support, it has a large user community who are always helping each other.

The last few versions work great out of the box without much config changes. Don't be afraid to try it.

It has the same features as paid-for databases such as Oracle and SyBase.

It's saved us money as it's free.

Eliminate the transaction wraparound possibility. If transaction wraparound occurs it can be a major problem.

I've used it for two years.

There were no issues deploying it for us.

We've experienced no issues with performance.

There have been no issues scaling it for our needs.

There is none available as it's a community driven solution.

It's simple to get it up and running.

We did it in-house.

We tested a big portion of our online API product using SoapUI and it was very fast and efficient.

Use this product for simple needs if you do not have PostgreSQL expertise. If you have PostgreSQL expertise you can run your business off PostgreSQL.