Increased database load on the secondaries since RC2
Since the deployment of RC2 the CPU usage on the secondaries has increased from around 20% to around 70%: ![postgres-stats](/uploads/87c4d9b6a363cb02c78233723717c7b7/postgres-stats.png) Looking at the tuple statistics one particular secondary shows this pattern: ![postgres-tuple-statistics](/uploads/21a4d3e691a65c2b3d617ff5be2d26c5/postgres-tuple-statistics.png) The big increase here is the number of sequentially scanned rows in the `users` table. This pattern occurs on both secondaries. This increase in load suggests we're doing something bad, something that might even affect availability if we don't solve it. cc @selfup @timothyandrew @smcgivern @DouweM @rspeicher
issue