PostgreSQL Reviews

• Hassle-free, low maintenance operation
• Free
• SQL compliance
• Slot-based streaming replication - live and purposely delayed are available
• Robustness
• Performance
• Low maintenance
• Decent Windows management GUI
• Cross-platform

It's improved security by allowing us to switch from an unsecure file-based database to a secure SQL database without license payments. Also, it provides us with multiple disaster recovery options with streaming replication.

It requires better management tools.

I've been using it for 12 years.

We have had no issues with the deployment.

It's been a stable product.

It's been deployed on >180 machines within the organization, ranging from Windows XP to Windows 2012 R2 and Ubuntu v12 to v16, and it's been stable.

Well worth the effort! I've been using it in my professional capacity without a single incident.

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.

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 can handle complex SQL queries.

It has helped to cut costs because it's open source.

It needs better support for JSON and web services.

I've been using it for 13 years.

We had no deployment issues.

We've had no stability issues.

There have been no issues scaling it for our needs.

It's open source, so there's no technical support available.

It was simple to setup.

We implemented it with our in-house team.

There was an immediate return-on-investment of 100%.

We also looked at MySQL and other databases including open source, standards, compliance, and enterprise features.

We have no regrets and are satisfied with it. I would advise you to go ahead and implement it.

We use the solution for database management and storage.

The most valuable feature is the performance.

The solution could improve the integration.

I have been using this solution for approximately four years.

I have found the solution to be stable.

PostgreSQL is a scalable solution. However, it could be better.

I have not needed to use the support.

The installation is not simple, it is more difficult than DeviceSQL. We had a few issues during the installation.

I did the implementation of this solution myself and it was more complex than MySQL.

I have evaluated MySQL and DeviceSQL.

I would recommend this solution to others.

I rate PostgreSQL an eight out of ten.

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.

• Updatable views (also over multiple tables)
• Array and JSON fields
• Point-in-time backup and recovery (WAL files archiving)

I find, sometimes, that it is too restrictive in cross-table/view constraints. This is very annoying as I needed to change a field definition from VARCHAR(10) to VARCHAR(30) and, having a group of views depend in it, the only solution was to implement a function that would:

• Read the view definitions
• Store them
• Delete the views
• Update the field definition
• Recreate the views

It took me like three or four hours (and caused a lot of stress) to make such a simple change. To me it looks a bit too overkill, especially nowadays that application requirements and implementation change so often.

I have used it for one and a half years.

There were no problems with deployment.

The app hasn’t had the need to scale much yet.

It was quite straightforward.

I implemented it myself and don’t have any particular advice about it. Today I would consider implementing it via Docker.

I've only used online open source resources and would say there's not as much as there is for MySQL. Sometimes it took me some time to find a good solution to the more unusual scenarios

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.