What problem does it solve?
It helps developers prevent slow queries, inefficient schemas, unstable performance, and security issues in Postgres—especially when building with Supabase—by enforcing practical, example-driven performance and correctness rules.
Core Features & Use Cases
- Postgres performance rule set across query, connections, RLS, schema, locking, and more: apply prioritized guidance with concrete “incorrect vs correct” SQL patterns to improve real workloads.
- Indexing and query-shape optimization: address missing, composite, covering, partial, and correct index types using precise SQL rewrites and examples.
- Operational and safety guidance for production: cover connection pooling, idle timeouts, prepared statements with pooling, vacuum/analyze, and deadlock/lock contention practices.
- RLS correctness and performance: build tenant-safe policies with patterns that avoid per-row expensive calls and support indexing.
- Use cases: query review and refactoring, migration/schema design support, performance diagnosis via EXPLAIN/ANALYZE, and RLS policy hardening for multi-tenant apps.
Quick Start
Ask an AI to “Use supabase-postgres-best-practices to review this query and propose the highest-impact fixes with incorrect vs correct SQL examples and the expected performance impact.”