neon-postgres-egress-optimizer

To reduce high Postgres egress data transfer costs, you must optimize queries by identifying inefficient data retrieval patterns like SELECT *, adding missing pagination, and applying structural changes to minimize network data transfer.

Your Postgres database has excessive egress from specific queries because of anti-patterns like unoptimized SELECT * statements, missing pagination on large result sets, or high-frequency queries fetching static data that could be cached or structurally optimized.

Yes, you need the pg_stat_statements extension enabled in your PostgreSQL database, as this Skill relies on it to identify which queries are transferring the most data and diagnose excessive network data transfer.

The best way to identify queries causing database egress is to analyze your codebase alongside query statistics to check for unused columns, missing pagination, and inefficient data retrieval patterns that drive up network data transfer.

You verify Postgres query optimization improvements by measuring the reduction in egress after applying fixes to anti-patterns, confirming that no remaining inefficient data retrieval patterns are causing excessive network data transfer.