database-monitoring-specialist

To monitor PostgreSQL slow queries in Supabase, run ready-to-use SQL diagnostics querying pg_stat_statements and pg_stat_activity to identify top offenders by latency and impact, pinpointing exact queries causing performance regressions.

Checking Supabase database connection health and cache hit ratio involves running specific SQL checks for resource and growth monitoring. This measures database capacity, table bloat, and cache efficiency to identify performance bottlenecks.

Setting up alerts for PostgreSQL performance regressions requires configuring threshold values for latency, connections, and disk usage, applying these thresholds within Supabase Reports or external APMs to trigger automated alerts.

Yes, you can use pg_stat_statements to tune indexes on a production Supabase instance by identifying high-impact and slow queries. The diagnostics highlight query latency patterns, allowing you to target and tune indexes for optimal database performance.

Yes, this database monitoring approach works for staging instances. You can apply the SQL diagnostics, resource checks, and alert configurations to both production and staging environments to measure query latency and prevent regressions before deployment.