pg-bloat-detective
Related Servers
Alternatives to pg-bloat-detective
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect and monitor PostgreSQL databases with read-only DBA tools for performance analysis, bloat detection, locks/deadlocks, autovacuum, schema discovery, replication, and maintenance recommendations.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to monitor and operate PostgreSQL databases through natural language queries, covering performance analysis, bloat detection, lock/deadlock monitoring, autovacuum and schema inspection, and maintenance recommendations with read-only, extension-optional workflows across PostgreSQL 12–18.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect and monitor PostgreSQL 12-18 databases through natural language, covering performance analysis, slow-query identification, bloat and lock detection, autovacuum health, replication/WAL status, and schema exploration. All operations are read-only and work without requiring any extensions, though pg_stat_statements and pg_stat_monitor optionally enhance query analytics.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to perform PostgreSQL operations and monitoring through natural language, including performance analysis, bloat detection, lock/deadlock monitoring, autovacuum inspection, schema discovery, and maintenance recommendations with production-safe read-only tools across PostgreSQL 12–18.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to perform PostgreSQL database operations, monitoring, and management via natural language, covering performance analysis, bloat detection, lock/deadlock monitoring, autovacuum and schema inspection with read-only production-safe queries.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to perform read-only PostgreSQL DBA analysis and monitoring through natural language, covering performance, bloat, locks/deadlocks, autovacuum, and schema inspection across PostgreSQL 12-18 without required extensions.-
TDQS
Scored across 5 tools
The set separates live collection (bloat_collect) from one-shot live diagnosis (bloat_live_diagnose) and from timeline readers (bloat_check, bloat_blockers, bloat_timeline). bloat_collect and bloat_live_diagnose return similar findings but descriptions clearly state saving vs discarding the snapshot. bloat_check and bloat_blockers overlap since check already reports blockers, though blockers adds focused pid/slot detail.
All names use snake_case with a consistent 'bloat_' prefix, making the domain and tool family immediately obvious. The pattern is predictable and no naming ambiguity exists.
Five tools is well-scoped for a focused diagnostic server: collect snapshot, check current state, live one-shot diagnosis, identify blockers, and show timeline. Each tool earns its place without redundant or missing core operations.
Coverage is strong for read-only PostgreSQL bloat diagnosis: collection, live diagnosis, timeline analysis, blocker identification, and current verdicts. Minor gaps exist around timeline management (pruning, export, listing snapshots) and remediation, though read-only safety appears intentional.