What problem does it solve? Investigating PostgreSQL issues during an incident requires knowing the right catalog queries for locks, replication lag, table sizes, and long-running queries. This Skill packages those diagnostic queries into ready-to-run scripts so you can inspect a database quickly without writing SQL from scratch. ## Core Features & Use Cases - Schema-First Exploration: List tables, describe columns with primary and foreign keys, and inspect indexes before running queries. - Safe Read-Only Queries: Execute SELECT, SHOW, EXPLAIN, and WITH statements with automatic row limits; DML/DDL and multi-statement queries are blocked. - Health Diagnostics: Detect lock contention and blocking queries, monitor replication lag on primaries and standbys, find long-running queries, and analyze table and index sizes. - Use Case: During an incident where the application is timing out, run get_locks.py to find blocking relationships, then get_long_running_queries.py to identify the offending query, all with credentials injected transparently by the proxy layer. ## Quick Start Ask the agent to list the tables in the PostgreSQL database and check for any blocking locks or long-running queries.
