Fixing Common PostgreSQL Performance Bottlenecks | Percona Community

In this article, I look at how poorly designed sharding systems and replication systems in PostgreSQL affect query performance in high volume situations, and how to ensure data consistency across many servers.  I also discuss how excessive vacuuming generates I/O traffic, and how connection pooling is used to improve transaction throughput by caching connections from clients.  I also cover how insufficient memory could affect PostgreSQL performance.  These are key problems I have encountered as a database consultant, and how I’ve overcome them.

This is a companion discussion topic for the original entry at

Comment by Philip Kumah Jr.:

This was quiet a read But worth the while. Thanks for this