Read-only PostgreSQL evidence collection
Limited query stats audit
pg_stat_statements disabled audit
Database Optimization Tool can still review schema, index, table, and maintenance evidence when pg_stat_statements is missing, while clearly marking weaker query coverage.
Local collector runs from your environment
Human review before production decisions
No database changes applied by Database Optimization Tool
Answer-first summary
When pg_stat_statements is disabled, query ranking gets weaker, but the audit can still find useful signals from indexes, scans, relation size, vacuum health, and temp-write symptoms visible elsewhere.
What the audit can still do without query stats
The audit can still review relation size, index usage, sequential scans, vacuum health, visible settings, and schema risks even without normalized query statistics.
How to interpret degraded query visibility
Findings that depend on query frequency or latency should be treated as lower-confidence leads until pg_stat_statements, logs, or application traces confirm them.
What this page cannot promise
Database Optimization Tool cannot reconstruct normalized query history without statement statistics, cannot enable the extension, and cannot claim exact query rankings from incomplete evidence.
Related topics
RelatedLinks for neighboring audit problems
Use these focused guides to compare query pressure, index decisions, and maintenance signals before you change production.
FAQ
Frequently asked questions
These answers stay inside the current Database Optimization Tool product boundary: read-only collection, evidence-gated findings, and human-reviewed next steps.
Can this run without superuser access?
Yes. Superuser is not required for every check, though missing privileges can reduce which non-query signals are available.
Can the audit return results without pg_stat_statements?
Yes. Without pg_stat_statements, the report still reviews indexes, tables, vacuum signals, and visible workload symptoms while marking query-stat coverage as degraded.
Why read the collector docs before running it?
The /docs/collector page explains what the local collector tries to read, how it exports evidence, and how disabled extensions affect coverage.
Why doesn't the report give commands to run immediately?
Degraded query visibility needs human validation. The report avoids direct production change commands when evidence is incomplete.