Postgres Performance
- Measure before optimizing.
- Inspect query plans and index usage when relevant.
- Look for N+1 access and unnecessary round trips.
- Consider cardinality, selectivity, locking, transaction scope, and data volume.
Use when investigating PostgreSQL query latency, query plans, indexes, locking, N+1 queries, transaction performance, or database bottlenecks.
npx skillmds@latest add rhenter/postgres-performance rhenter/agent-skills/tree/main/skills/postgres-performance commit d24a327bca