One Autovacuum Away: Partitioning slice’s Billion-Row Transaction Tables Without Downtime

Preface One evening Postgres ran a routine ANALYZE on one of our tables. Within minutes, one of our payment products was degraded. Nothing had been deployed. No migration, no config change, and traffic was normal. Yet the database writer was saturated, latency on the transaction API had climbed into seconds, and pods were cycling through readiness checks. The slow log had one line worth reading:…

This is an excerpt. The full article continues at Slice.