PostgreSQL Reviews

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.

PostgreSQL gives you much more flexibility because it's open source.

It improves the query performance a lot and helped in some real time and analytic reporting

Sometimes it hangs and then we need to stop and start the services again

I've used it for three years.

We've had no issues with the deployment.

There have been no stability issues.

We have had no issues scaling it.

7.5/10

7.5/10

No other solution was used.

It was straightforward.

We used a vendor team.

The h-stores are very powerful for handling collections of key-value pairs. The query syntax and functions are well documented and easy to use.

PostgreSQL is a powerful and open source database, which is central all data processing.

We'd like to be able to start using JSON objects for easy code representation. This feature is available in v10.4.

I've been using it for eight years.

We've had no issues with the deployment.

There have been no stability issues.

It's been able to scale for our needs.

I use online documentation, which met my needs.

We were using version 8 before, and also an earlier Oracle instance. We chose the product because it is powerful, well documented, and open source.

I did not set up the actual installation. I did set up the schema, tables, foreign keys, etc. That was straightforward in that it was well documented.

In house. You do need someone that knows PostgreSQL or that can spend time learning about the product.

It's open source. ROI is a matter of time.

The challenge with this product would be finding the IT resource that can implement the product.

Open source products represent no cost to the organization and the basic features are sufficient to fulfill our needs.

• Cost savings
• Easy spin off for new environments

The only feature where I can see an area of improvement is with the partitioning. As soon as you implement partitioning, all your relationships are no longer supported since the PK-FK relationship is no longer supported and you need to look for options or database changes to supported with secondary tables, database rules or triggers.

I've used this solution for two years. We also use the EnterpriseDB version of PostgreSQL.

There were no issues with the deployment.

We had no issues with the performance.

It's been able to scale for our needs.

We have no external services.

We haven't used any other open-source service, but we have engaged Enterprise DB for enhancing our monitoring but there was no need to do so.

I wasn't in my current organisation when it was implemented.

We use the open source versions of PostgreSQL so there is no expense for licensing.

Do continuous testing and research on new features as they have an excellence performance response.

• Confidentiality
• Integrity
• Availability
• Bug free

I like to work with a piece of software that is bug free and doesn't required to be launched in order that users will find a couple of bugs in the coming weeks and that the company has to fix it.

It helped me to find an easy and inexpensive solution for databases

It would be interesting to have a cloud based database instead of having to install it on any single machine.

I've used it for approximately one to two years.

I've had no issues deploying it.

The stability was an issue, because when coding under Eclipse with Java, some errors occurred while trying to connect to the database, so troubleshooting may be difficult, since you don't know if it's a Java coding issue or a PostgreSQL translation issue.

There have been no issues scaling it.

I never used any customer service or technical support during that time. I used to find alternatives to my issues.

Since Oracle was expensive for a company business an inexpensive way was to focus on PostgreSQL.

The initial setup was straightforward, just activating various modules was more complex.

We did it in-house.

I saved money instead of using the Oracle solution, which might be more secure than PostgreSQL in various ways.

You need to find a lot of time in order to find all functionality and get used to the PostgreSQL syntax Be patient, look for various forums and do learning by doing.

The reason why I started with PostgreSQL database was the (geo)spatial support. GIS software, such as Quantum GIS (QGIS) or PostGIS, is a good example of where you are able to use this feature. Nowadays, the solution is on a competitive level to other commercial software solutions, especially for small companies.

PostgreSQL (geo)spatial support is stable, and you can add, remove, and edit all standardized GIS features. Thanks to projects such as EDB, Bitnami etc., PostgreSQL can be used by people on pure user level, without deep knowledge of OS administration, programming.

There is room to improve some user friendly properties such as input and output tools, some people may find interesting to implement MERGE as a SQL command. I am looking forward to trying UPSERT and would like to test some analytic functions definitely.

I've been using v9.4 for a half year. I also have experience with previous versions of PostgreSQL. Currently we have PostgreSQL 9.4.7 on Fedora Server 23 and PostgreSQL 9.4.5 packaged by EnterpriseDB (EDB) on Windows 10 Pro.

I had trouble with the reinstallation of EDB. If I have a previous version on my Windows PC, I have to take some steps to clean the registries and folders, then everything is OK.

If you are interested in you can find answers for troubleshooting. Many companies, I have mentioned above, are there for service and support. I didn’t find any big bug in the latest stable release over the last few months.

If you are interested in you can find answers for troubleshooting. Many companies, I have mentioned above, are there for service and support. I didn’t find any big bug in the latest stable release over the last few months.

I recommend Linux installation, but it is also possible to use Windows. With PostgreSQL you don't have to pay much money which is a good advantage. You have to take into account that you will spent some time finding out how to implement something or what is the right tool you have to use.

PostgreSQL is a long-lasting investment for people who like computers and don’t want to spent much money for database layer implementation.

JSON data support is most valuable to me as it saves design and maintenance time. It is a very safe and stable solution.

We are spending less time parsing API response and more time exploring data. We spend time understanding APIs and how to interact with them, If we can load responses directly to the database that saves many man hours for a project.

A better export facility which is GUI friendly would be an improvement. Also if we could export data from grid that would have been helpful.I have used HeidiSQL for MySQL which is very user friendly, pgAdmin III is not that helpful when it comes to different features we need to use like export,filtering and connections.

I've been using it for one year and am still exploring it.

We had no deployment issues.

We had no issues with the stability.

We had no issues scaling it.

I have worked with MySQL, Microsoft SQL, db2, and Oracle. We chose PostgreSQL for its JSON support as our APIs are sending JSON responses and PostgreSQL is like home for JSON. Choosing it has helped our cloud computing requirements a lot.

On Windows it's straightforward, but on Ubuntu, it was a bit complex when it came to database and tablespace division through PSQL.

We did it in-house.

If you are thinking of using PostgreSQL, all database names, table names and column names should be in small letters. PostgreSQL requires every capital letter to be quoted which makes life difficult for developer.