supabase-postgres-best-practices

To optimize PostgreSQL queries causing slow sequential scans, you can apply expert rules for index selection and query rewriting to reduce execution time by orders of magnitude. This skill identifies the correct index type to replace sequential scans on large tables.

The best way to manage connection pooling for a Supabase database is to apply actionable rules for connection management. This ensures high availability and low latency during database performance tuning and infrastructure scaling.

Schema design affects PostgreSQL performance by dictating data types, partitioning, and constraint implementation. Applying schema best practices ensures long-term database health and prevents inefficient query patterns that cause resource exhaustion.

Choosing the right index type for PostgreSQL tables involves analyzing query execution plans and applying expert-curated optimization rules. This skill guides index selection to resolve performance bottlenecks and improve application response times.

You can use these optimization rules for both standard Postgres and Supabase environments. The performance tuning, connection pooling, and schema architecture guidance applies to database development and infrastructure scaling across both platforms.

Supabase RLS policies can cause query performance issues when not optimized correctly. This skill provides specific rules for RLS policy optimization to ensure that row-level security does not lead to slow application response times.