neon-postgres-egress-optimizer

From README

Postgres Egress Optimizer Guide the user through diagnosing and fixing application-side query patterns that cause excessive data transfer (egress) from their Postgres database. Most high egress bills come from the application fetching more data than it uses. Work the four steps in order: diagnose which queries transfer the most data, analyze the codebase behind them, fix the anti-patterns, then verify nothing broke and the transfer actually dropped. Step 1: Diagnose Identify which queries transfer the most data. The primary tool is the pgstatstatements extension. Check if pgstatstatements is available If this errors, the extension needs to be created: On Neon the extension is available by default, but it may still need this CREATE EXTENSION step. Handle empty stats Stats are cleared when a Neon compute scales to zero and restarts.