There are plenty of small installations of PostgreSQL that happily run without much planning or maintenance. But as your data and user count grows, the amount of work needed to keep things running will too. Those changes don't have to be a surprise though; there are several common growing pains you can prepare for if you know about them in advance. This tutorial will outline the causes and solutions to the most "popular" scaling problems PostgreSQL installations go through, as they go from megabytes to terabytes and from one user to thousands.

Topics will include:

• System monitoring
• Query log analysis
• Vaccum and table cleanup
• Cache priming
• Benefits of partitioning
• Planning for read-only replicas and pooling