A collection of 34 diagnostic SQL reports for PostgreSQL DBAs, accessible directly within psql with no external dependencies.
postgres_dba is a collection of 34 diagnostic SQL reports designed for PostgreSQL database administrators and engineers. It runs entirely within psql, providing instant insights into database health, performance, bloat, locks, corruption, and indexes without requiring external agents or daemons. The tool solves the problem of fragmented monitoring by centralizing essential checks into a single, command-line accessible toolkit.
PostgreSQL database administrators, backend engineers, and DevOps professionals responsible for maintaining, optimizing, and troubleshooting PostgreSQL databases in production or development environments.
Developers choose postgres_dba because it offers zero-dependency, immediate access to production-grade diagnostics directly in psql, eliminating setup complexity. Its comprehensive report coverage—from bloat estimation to corruption checks—combined with ease of use (just type `:dba`) makes it a unique, lightweight alternative to heavier monitoring solutions.
The missing set of useful tools for Postgres DBAs and all engineers
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Runs entirely within psql without external agents or daemons, as emphasized in the README's 'just SQL' philosophy and quick start setup.
Offers 34 curated reports spanning bloat estimation, corruption checks, lock trees, and vacuum monitoring, addressing critical DBA tasks in one toolkit.
Simple installation via git clone and psqlrc modification allows instant access by typing `:dba`, eliminating complex deployment steps.
Users can add custom SQL scripts in the sql/ directory and regenerate the menu with generate.sh, as documented in the 'Adding Custom Reports' section.
Full functionality requires extensions like pg_stat_statements and amcheck, which may not be installed or enabled in all environments, limiting report availability.
Reports such as b3 and b4 use pgstattuple, noted as 'expensive' in the README, and can read all data, potentially slowing down active databases.
Tied exclusively to psql, making it unsuitable for users who prefer graphical tools or need integration with web-based monitoring systems.