PostgreSQL Reviews

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.

The spatial extension, PostGIS, is amazing and probably the gold standard. I also like the Key-Value column type and the JSON column type. Apart from this, it has all the other features you will need in an RDBMS and then some. It has a vibrant FOSS community with a great license and it has plenty of books and documentation

Rather than using Desktop GIS software we were able to carry out a lot of our spatial operations faster with larger datasets by moving the operations into PostgreSQL. We also save a ton of money on Oracle licenses. Finally, rather than having to give up my relational features, I can use the JSON data type and get everything I want.

They need to work towards making it work better in a cloud environment. Also, I would love to see them developm multi-master replication.

We have had no issues with the deployment.

There have been no performance issues.

It's been able to scale for our needs.

Get a good book so you can get exposed to all the great functionality in PostgreSQL. I would highly recommend looking at the postgresql.conf configuration settings when you are ready to go into production.

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.

It supports full text search, and windows functions.

All our data is stored in PostgreSQL, and we use a BI solution on top to gather all the important metrics to our business, so the whole company has a clear picture of what is going on.

It lacks the ability to distribute queries across multiple installations out of the box.

I've used it for seven years.

No issues encountered.

I've never experienced any data loss.

No issues encountered, even when querying through third-party applications.

Customer Service:

I've never had to deal with customer service.

Technical Support:

The support in the community is excellent, the documentation is great, and questions submitted to the mailing list are quickly answered. The IRC support is also excellent.

I used MySQL, but I needed support for full text search. PostgreSQL adds this, and also many more advanced SQL functions.

Setup was very easy on all platforms that I use - Linux, Mac OSX, and Windows. It is a simple walk-through installation.

It was done in-house.

It's a free solution, and we use it as a data store, it's all return.

PostgreSQL is free software. The only cost of setup was a few developer hours, and with it being stable, we don't have any day-to-day costs.

• MySQL
• Microsoft SQL Server

PostgreSQL is one of the most stable data sources out there, and it offers you the most advance and modern functions on SQL so you can do more with less.

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.

The SQL is very close to the standard, the richness of of procedural languages and the strong attitude to the data reliability.

The product is used to ensure the data delivery and the HA features are used to enforce a non stop service.

The partitioning, is still very basic and not touched for years.

7 years

More a lack of knowledge rather an issue. PostgreSQL implements the data management in a very peculiar way. Ignoring this can result in disasters. And often this does happens. A better explanation about the architecture will reduce the risk.

Not on the production side. I’ve seen a lot of bugs or misconceptions on the HA side. Same as question 7, It’s more a lack of information than an issue.

The product scales pretty well.

Customer Service: As this is an community managed system there’s no customer service. There are companies offering support, I never used as I don’t need it.Technical Support: Quite good. The mailing list are a good way to have quick response. What really lacks is a centralized knowledge base like the Oracle’s metalink/otn. That is what I’m really missing from the oracle universe.

I worked for years on Oracle. I decided to move on PostgreSQL because I think is a first class product.

Using the packaged way is almost immediate to install the product. Even the compile from source is a task any system administrator or advanced linux user can do it without any problem.

It’s an in house team.

Basically zero for both. The product is released under the BSD license and, apart from my salary, my employer have no extra costs on using PostgreSQL

I considered in the past MySQL and Firebird.

Employ a DBA to work together with the developers.

Out of all the open source database applications available, PostgreSQL is among the best DB storage engines with a single unified database server unlike MySQL which supports multiple storage engines for storing the data. PostgreSQL was specifically designed and developed with a focus on features and standards whereas MySQL was designed with a focus on speed. So, if you are looking for a large number of features and support for various standards, then PostgreSQL is the answer. PostgreSQL supports scalability on write intensive tasks. It also supports asynchronous commit, which is generally missing from other similar DB applications. It is fully ACID compliant.

PostgreSQL does not multiple back-end storage engines unlike MySQL. It does not perform well when dealt with read-only DB queries. It is not very efficient in handling COUNT(*) queries. PostgreSQL does not support queries like 'INSERT IGNORE', which inserts if a row doesn't exist, and 'REPLACE' which replaces the current row, both of which are supported by MySQL. Another query missing from PostgreSQL is "INSERT ... ON DUPLICATE UPDATE ". PostgreSQL does not have an unsigned integer data type. PostgreSQL is limited to 32 columns per index.

PostgreSQL is one of the best open source DB storage application which supports only one backend storage engine. PostgreSQL is well known for the number of features it supports and the standards followed. PostgreSQL is pretty slow when dealing with queries like COUNT(*) and many of the queries like 'INSERT IGNORE', which inserts if a row doesn't exist, and 'REPLACE' which replaces the current row. It is also limited to 32 columns per index. If you are looking for a speed, then you have to look for other DB engines available e.g. MySQL.