evidence-focused PostgreSQL evidence collection
No-superuser audit
Postgres audit without superuser
Database Optimization Tool helps teams collect useful performance evidence when superuser access is unavailable, inappropriate, or blocked by a managed provider.
Local collector runs from your environment
Human review before production decisions
No database changes applied by Database Optimization Tool
Answer-first summary
You do not need superuser access for every Postgres performance audit. You do need honest coverage notes when privileged evidence is unavailable.
Why a one-time audit can start below superuser
A one-time audit can start with non-superuser access because many catalog, size, index, and statistics views are readable below privileged roles.
What decisions still need human validation
Index changes, extension changes, parameter changes, and maintenance scheduling still need human validation because limited evidence can miss workload context.
What this page cannot promise
Database Optimization Tool cannot bypass role design, install extensions, inspect host files, or make privileged changes on your behalf.
FAQ
Frequently asked questions
These answers describe the product focus: careful database evidence, clear findings, and team-approved next steps.
Can this run without superuser access?
Yes. Many performance issues are visible through normal PostgreSQL catalogs and statistics views below superuser.
Can the audit return results without pg_stat_statements?
Yes. Missing pg_stat_statements reduces query-level confidence, but table, index, size, and vacuum evidence can still produce useful results.
Why read the collector docs before running it?
The /docs/collector page shows the expected grants, local export steps, and how missing permissions are represented in the evidence.
Why doesn't the report give commands to run immediately?
The report highlights review targets, not direct production commands. Human validation is required before privileged or workload-sensitive changes.