neon-postgres-egress-optimizer Skill

Source

• Creator: openai
• Repository: openai/plugins
• Skill file: plugins/neon-postgres/skills/neon-postgres-egress-optimizer/SKILL.md

What it does

Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs, network transfer charges, egress spikes, "why is my Neon bill so high", "database costs jumped", SELECT optimization, query overfetching, reduce Neon costs, opt

Skill instructions

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. Step 1: Diagnose Identify which queries transfer the most data. The primary tool is the pgstatstatements extension. Check if pgstatstatements is available sql SELECT 1 FROM pgstatstatements LIMIT 1; If this errors, the extension needs to be created: sql CREATE EXTENSION IF NOT EXISTS pgstatstatements; On Neon, it is available by default but may need this CREATE EXTENSION step. Handle empty stats Stats are cleared when a Neon compute scales to zero and restarts. If the stats are empty or the compute recently woke up: 1. Reset the stats to start a clean measurement window: SELECT pgstatstatementsreset(); 2. Let the application run under representative traffic for at least an hour. 3. Return and run the diagnostic queries below. If th