Where **not** to use PostgreSQL?

 

Postgres has made great strides in adding features to match proprietary databases, and it has many complex features that other databases don't have.

However, that doesn't mean it is the best fit for every organization. There are still reasons *not*  to use Postgres:

• Skills in another relational database, and no desire or value to learn Postgres
• Custom applications written for another database that you don't want to modify to work with Postgres
• Using externally-developed applications, tools, or frameworks that don't support Postgres
• Storage of non-transactional or cache data where Postgres's overhead is significant
• Multi-host workloads with simple queries where NoSQL is a win

This email thread had lot of discussion on the topic. What is interesting is that decades-old complaints about missing features, reliability, and performance are no longer mentioned.