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 allowed us to run a Scada database, which reads data every 2 minutes. It does it in a very smooth way.

I would like to have better support for real-time applications.

I've been using it for three years.

No at the time. Our application fits very well.

No at the time. Our application fits very well.

No at the time. Our application fits very well.

I have used online free help.

MySQL but not in the same scale.

We implemented it in-house.

Analyze very carefully the hardware requirements.

HStore is a data type in PostgreSQL database that gives the flexibility for storing sets of key/value pairs which is quite an awesome feature.

Slow count. As the number of rows exceed a couple million, the count query and queries which get to the depth of the data (like FTS) start taking too much time even with all the right indexes in place.

I've used it for two and a half years.

We use RDS Multi - AZ deployment which takes care of it all for us.

We've had no stability issues.

There have been no issues with scalability.

I've never had an issue with the product, and therefore never had to reach out.

We tried RethinkDB a couple of years back, and it was unstable at that time. Also, MySQL didn't have a JSON type back then. We switched to PostgreSQL and never looked back.

I do remember facing problems with the initial setup, but the overall documentation and SO answers has increased since then. New users face much less problem now. But there is still scope for improvement here.

I'd recommend reading Greg Smith's PostgreSQL High Performance.

Before PostgreSQL, I am an avid user of MySQL for a long time. When I began my masters in a renowned school, I was introduced to PostgreSQL and started to like it. Here are the few things I have loved about Postgres: • It is free and compatible in all platforms • It performs very quickly and can outperform Oracle, SQL server and IBM DB2 • It uses SQL windowing functions which are rarely found in other open source database platforms • It uses CREATE EXTENSION which can easily extend without changing the database structure and no code compilation • It has multiple programming languages such as SQL, PL/pgSQL, PL/Perl, PL/Python, PL/Java, and PL/R etc. • The custom type support is very easy to use and very sophisticated which competes Oracle in terms of performance

• Windows versions were released ten years after the initial release • Replication is not so powerful in later versions • Postgres is not so popular compare to MySQL • PostgreSQL community has lesser support

I cannot stress how highly I recommend PostgreSQL to my fellow programmers. The features and functionalities are beyond the abilities of other free database platforms and are comparable to the proprietary ones. Some advanced features may also be seen to the license databases but you’ll amaze how advance PostgreSQL may become in the future but in zero cost.

It works great out-of-the-box and it opens up many opportunities in project development.

I first install the regular version. I only configure complex things when they are needed.

I think that the product fully meets the needs of modern development. If there is something missing in it, then it is probably a too narrow profile function.

I've used this solution for two years.

There were no issues with stability.

There were no issues with scalability.

I would rate the technical documentation as an eight out of 10. I never spoke with the support team.

I used MySQL. I switched because at that time, because some things were complicated with MySQL. For example: scaling, sparse data JSON, and other issues.

Both projects have the same query syntax, and the transition for me was almost painless.

The setup was easy.

As far as I know, there are no problems with the license for free use.

I explored many different databases: Redis, MongoDB, MySQL, Elasticsearch, and others.

I use some of them in conjunction with PostgreSQL. However, if we are talking about relational databases, then I only use MySQL.

I think this is the only decent solution for a relational database in web development.

I have not used any enterprise PostgreSQL product. I have only used the open-source version of PostgreSQL. I like the following features:

• Locking: Tables very rarely get locked, while with MySQL, it’s a frequent problem.
• Easy backup and restore
• Reporting uses Windows functions / aggregates function
• Partitioning

By implementing PostgreSQL, organizational databases get stabilized, no locking issues occur and report extraction is faster.

I would to see the following improvements:

• Replication: Table-level replication should be built-in. However, we can do this now by using Slony.
• Backup: Currently, an incremental backup feature is not available. It should be added.
• A simple-to-use PG cluster monitoring dashboard would provide an extra advantage.

So far, it’s the best database I have ever used.

It allows us to have an alternative solution to licensed DB's.

It requires enterprise integration improvements from the security, and audit perspective (AD integration etc.). Also, integration into existing BI tools is not present.

I've used it for three years.

They provide a high level of technical support.

We switched due to a common OS integration strategy.

We had an RFP process to evaluate between similar product categories.

Backend: 64-bit large objects, Cascading streaming replication, Serializable Snapshot Isolation; Performance:GIN Index performance and size improvements; Security: SSPI authentication via GSSAPI; list goes on...

Automation, accurateness and concistency of enterprize processes

Comercial & Supply Chain

9 years

No

No

No

Customer Service: 9Technical Support: 9

MySQL: scalability; Oracle: cost-benefit

Easy and straightforward

in-house

36%

Oracle and MSSQLServer

I suggest to anyone give it a shot. It'll make your business grow.