Read-only Neon Postgres evidence collection
Neon audit
Neon Postgres audit
Database Optimization Tool reviews Neon PostgreSQL evidence while accounting for managed roles, branching workflow, and serverless connection patterns.
Local collector runs from your environment
Human review before production decisions
No database changes applied by Database Optimization Tool
How to audit bursty workloads on Neon
A Neon audit should focus on SQL-level workload evidence and branch context. Database Optimization Tool helps separate query and index risk from platform behavior that the database role cannot prove.
Environment limits
Neon may limit privileged settings, host metrics, and role capabilities. Branches and pooled connections can also affect what a point-in-time evidence snapshot means.
What read-only evidence still matters before plan changes
The collector can read schema shape, relation size, index usage, table activity, autovacuum evidence, and pg_stat_statements when enabled and readable.
What this page cannot promise
Database Optimization Tool cannot infer hidden compute events, change Neon configuration, or replace staging validation before you ship index or SQL changes.
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.
Does a Neon audit require superuser?
No. Database Optimization Tool expects a safe database role and reports what it can prove from readable Neon catalog and statistics views.
What if pg_stat_statements is unavailable on Neon?
The audit still reviews schema, index, table, and maintenance signals, but query ranking is less complete without readable pg_stat_statements data.
Will Database Optimization Tool make production changes to Neon?
No. It collects read-only evidence from the branch connection string you provide and leaves production database changes to your team.
When should I read /docs/collector or /sample-report?
Use /docs/collector before collecting a Neon snapshot, and use /sample-report to understand how bursty workload caveats and read-only findings appear.