g14wxz/db-diagnostics-inspection
Provides database health diagnostics via slow query analysis, bottleneck identification, and Postgres inspection.
100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Securityby
Passed
No known issues
Db Diagnostics Inspection
Provides database health diagnostics via slow query analysis, bottleneck identification, and Postgres inspection.
Overview
This tile enables agents to inspect Supabase Postgres health using system catalog views. It targets pg_stat_statements for query performance, pg_stat_user_tables for table-level I/O patterns, and pg_stat_user_indexes for index utilization. All queries run through the MCP execute_sql interface. The inspection is strictly read-only.
Reference
| Catalog View | Purpose |
|---|---|
pg_stat_statements | Query execution times, call counts, row counts |
pg_stat_user_tables | Sequential vs index scans, dead tuples, vacuum status |
pg_stat_user_indexes | Index scan frequency, tuple reads/fetches |
pg_stat_activity | Active connections, idle sessions, query states |
pg_locks | Lock contention and blocked queries |
Key Thresholds
- Slow query:
mean_exec_time > 100ms - Missing index:
seq_scan > 1000ANDidx_scan = 0 - Vacuum backlog:
n_dead_tup > 10000 - Connection pressure: active connections > 80% of
max_connections
Dependencies
- supabase-mcp-verification (root prerequisite) — MUST pass before any diagnostic query executes.
- pg_stat_statements extension — MUST be enabled on the target database.
Composition Position
- Stage: database-observability
- Priority: MEDIUM
- Runs after MCP verification. Produces diagnostic reports consumed by remediation or alerting tiles downstream.
- Workspace
- g14wxz
- Visibility
- Public
- Created
- Last updated
- Publish Source
- CLI
- Badge
