Read-only collector
Sample report
Sample PostgreSQL audit report
A realistic report structure for small teams: accepted findings, evidence, operational risk, next actions, and a separate AI advisory layer.
Evidence-gated findings
Human review before production changes
P1: Sequential scan pressure on public.orders
Evidence: high seq_scan and seq_tup_read relative to indexed access. Recommendation: run EXPLAIN (ANALYZE, BUFFERS) on the top order lookup query before adding a composite index.
P1: Temp writes in a top query
Evidence: temp_blks_written is present on a high total_exec_time query. Recommendation: inspect sort/hash operations and test work_mem or index changes in staging first.
P2: Unused non-unique index candidate
Evidence: index size is material and idx_scan is zero. Recommendation: compare dependency and query coverage before dropping or rebuilding any index.
AI Upgrade Lab advisory
The AI section is plain text advisory only. It proposes read-only diagnostics, reversible index experiments, verification checks, and rollback notes without changing evidence-gated findings.
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.
Why does the sample report mention EXPLAIN before index changes?
Database Optimization Tool treats EXPLAIN evidence as the checkpoint between a plausible idea and a production-ready recommendation.
Can the report surface temp write pressure?
Yes. Query findings can include temp_blks_written and related pressure signals so teams know when sorts or hashes are likely spilling to disk.
Does the sample include table maintenance signals?
Yes. The report format is designed to keep query findings, index candidates, and autovacuum or dead-row warnings in the same review flow.
Can I compare this sample with a real collector upload?
Yes. Use the sample to understand the report shape, then run the collector locally and upload your own audit.json for account-protected analysis.