How does it handle connection pool monitoring?

It identifies connections stuck in 'idle in transaction' states and provides SQL for killing leaked backends that prevent new connections.

Does this skill require specific PostgreSQL extensions?

It is designed to work best with pg_stat_statements enabled to track cumulative execution time and query frequency.

When should I use the Supabase Advanced Troubleshooting skill?

Use it when standard debugging fails, specifically for performance regressions, race conditions, connection pool exhaustion, or complex RLS failures.

Can it help diagnose why rows are missing in query results?

Yes, it includes advanced RLS conflict analysis to identify if policies are silently filtering data or if permissive/restrictive policies are clashing.

Does this skill help with Supabase Edge Functions?

Yes, it provides guidance on profiling Edge Function cold starts and investigating latency issues using the Supabase CLI.

Supabase Advanced Troubleshooting

Name: Supabase Advanced Troubleshooting
Author: jeremylongshore

byjeremylongshore

•

1,887

•

Database Management

Diagnoses and resolves deep PostgreSQL performance issues, connection leaks, and RLS conflicts within Supabase environments.

This skill provides a comprehensive toolkit for advanced Supabase diagnostics, moving beyond basic debugging to solve complex performance regressions and production bottlenecks. It leverages PostgreSQL system catalogs like pg_stat_statements and pg_locks to identify slow queries and lock contention, detects silent data filtering in RLS policies, and profiles Edge Function latency. Whether you are investigating connection pool exhaustion or intermittent Realtime drops, this skill offers the precise SQL queries and SDK patterns needed for deep-stack troubleshooting and support escalation.

Key Features

01Lock contention and deadlock detection via pg_locks monitoring

02Performance monitoring wrappers for the Supabase JS SDK

03RLS policy conflict debugging with role-based simulation

04Connection leak identification through pg_stat_activity analysis

05Slow query analysis using pg_stat_statements and EXPLAIN ANALYZE

061,887 GitHub stars

Use Cases

01Identifying the root cause of production database timeouts and query regressions

02Debugging silent data access failures caused by complex or overlapping RLS policies

03Detecting and clearing leaked database connections that exhaust the pool

Key Features

01Lock contention and deadlock detection via pg_locks monitoring

02Performance monitoring wrappers for the Supabase JS SDK

03RLS policy conflict debugging with role-based simulation

04Connection leak identification through pg_stat_activity analysis

05Slow query analysis using pg_stat_statements and EXPLAIN ANALYZE

061,887 GitHub stars

Use Cases

01Identifying the root cause of production database timeouts and query regressions

02Debugging silent data access failures caused by complex or overlapping RLS policies

03Detecting and clearing leaked database connections that exhaust the pool