supabase-postgres-best-practices

Fix slow Postgres queries by applying prioritized rules for query rewriting, selecting composite or covering indexes, and resolving N+1 batch access patterns using provided anti-pattern and best-practice SQL examples.

Configure connection pooling by applying best practices for pooling, timeouts, and prepared statements in pooled environments to ensure connection and locking safety. This prevents connection exhaustion and maintains database stability under load.

Row-Level Security (RLS) can degrade Postgres performance if policies are poorly written. Tune RLS by applying performance optimization guidance to refactor policies, ensuring throughput remains high while maintaining strict security constraints.

You need partial or covering indexes for JSONB data when query patterns filter on specific JSON keys or require specific columns without hitting the table. The Skill guides index selection for JSONB and Gin scenarios to maximize query speed.

Avoid Postgres migration safety issues and deadlocks by applying consistent ordering in transactions and following locking safety best practices. The Skill provides operational guidance to prevent deadlocks and ensure stable schema changes.

Yes, you can use keyset pagination instead of offset for large Supabase tables to improve performance. The Skill provides pagination strategy guidance as part of its operational best practices for scaling Postgres environments.