Read-only scope
No production writes, no DDL, no index creation, no data cleanup, and no automatic tuning changes.
Local collector
Use a PostgreSQL collector path that keeps production writes out of scope.
The collector model is for evidence gathering: catalog metadata, statistics, table health signals, index usage, role posture, and workload pressure. It should not modify database state.
Collector boundaries.
The safest first audit uses temporary, least-privilege access and a local run path that can be revoked after review.
Local evidence
Collect from system catalogs and statistics such as query activity, relation sizes, index usage, dead tuple signals, and maintenance timestamps.
Temporary access
Prefer a dedicated audit role with limited visibility and a clear removal plan after the audit is complete.
Confirm goal
Define whether the audit is for launch readiness, slow checkout, reporting latency, capacity planning, or a general tuning pass.
Collect signals
Capture slow query pressure, table and index size, unused index candidates, bloat risk, vacuum health, temp writes, and role review signals.
Keep output reviewable
Store findings as a report that a developer, DBA, or specialist can challenge before any production change is scheduled.
Escalate when needed
Use the specialist PostgreSQL service for hosted workflow, account handling, pricing, or transaction support.
Boundary note
This category page explains the collector path. It does not provide hosted accounts, payment flows, or a production execution system.