supabase-advanced-troubleshooting

Diagnose PostgreSQL performance issues and connection leaks in Supabase environments.

5|Updated Jan 20, 2026

Search Tags:#performance #debugging #troubleshooting #postgresql #rls #supabase

Ready to run

npx skills add https://github.com/mohamedgshoaib/reway --skill supabase-advanced-troubleshooting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: supabase-advanced-troubleshooting
Source: https://github.com/mohamedgshoaib/reway/tree/main/.agents/skills/supabase-advanced-troubleshooting
Command: npx skills add https://github.com/mohamedgshoaib/reway --skill supabase-advanced-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves complex, non-obvious issues in Supabase projects, such as persistent performance regressions, silent RLS filtering, and connection pool exhaustion, which standard monitoring tools often miss.

Core Features & Use Cases

Advanced Diagnostics: Utilizes pg_stat_statements and pg_locks to pinpoint slow queries and lock contention.
Leak Detection: Identifies and terminates idle-in-transaction connections that exhaust the pool.
Use Case: When your application experiences intermittent latency spikes, use this skill to profile Edge Function cold starts and analyze RLS policy conflicts to ensure data is being filtered correctly.

Quick Start

Use the supabase-advanced-troubleshooting skill to identify the top ten slowest queries by execution time in your database.

Frequently Asked Questions about supabase-advanced-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find slow PostgreSQL queries causing latency spikes in Supabase?▼

To find slow PostgreSQL queries in Supabase, you can use diagnostic skills that leverage the pg_stat_statements extension to pinpoint queries with the highest execution times. This identifies the exact operations causing latency spikes.

Why does Row Level Security silently filter data in Supabase and how can I resolve it?▼

Row Level Security (RLS) silently filters data when policies conflict. Diagnosing RLS policy conflicts involves analyzing your Supabase database permissions to ensure data is being filtered correctly without causing unintended access restrictions.

How do I detect and terminate idle-in-transaction connections exhausting my Supabase pool?▼

To detect connection leaks in Supabase, identify and terminate idle-in-transaction connections that exhaust the connection pool. This resolves persistent performance regressions by clearing blocked database resources.

Do I need the pg_stat_statements extension enabled to troubleshoot Supabase database performance?▼

Yes, you need the pg_stat_statements extension enabled and direct database access via SQL Editor or psql to perform advanced Supabase troubleshooting. This extension is required to track query execution statistics and identify slow operations.

What is the best way to diagnose lock contention in a Supabase PostgreSQL database?▼

The best way to diagnose PostgreSQL lock contention in Supabase is by utilizing the pg_locks view to pinpoint blocking transactions. This allows you to identify and resolve complex non-obvious issues like connection pool exhaustion.