Business symptom
Name the slow workflow, affected users, error rate or timeout pattern, and when the problem became visible.
Request preparation
Prepare a database optimization request before anyone changes production.
Use this checklist to turn a slow database complaint into an audit-ready brief: symptom, engine, evidence, risk limits, access boundary, and next step. It works as a broad preparation page before PostgreSQL-specific routing.
Checklist
Prepare these inputs first
You do not need every item. The goal is enough context to decide which evidence matters next.
Database context
List the engine, version, hosting model, approximate size, traffic pattern, and recent migrations or deploys.
Query evidence
Bring representative slow queries, execution plans, logs, statement statistics, or screenshots your team can safely share.
Schema and index context
Prepare major table sizes, relevant indexes, known unused indexes, write-heavy tables, and constraints around index changes.
Safety constraints
State whether production access is allowed, whether only read-only evidence is acceptable, and what data cannot be shared.
Approval path
Identify who can approve tests, who can approve production changes, and what maintenance window or rollback plan is required.
Flow
How the request should move
The process should narrow scope before collecting more evidence or proposing production work.
Describe the symptom
Start with the workflow, user impact, timing, recent changes, and whether the issue is urgent or recurring.
Attach safe evidence
Share logs, plans, table sizes, index context, or read-only statistics that do not expose secrets or unrestricted customer data.
Confirm boundaries
Define read-only expectations, data sensitivity, allowed environments, and changes that require explicit approval.
Pick the right route
Use the broad audit page for preparation. Use the PostgreSQL path when the database is PostgreSQL and a specialist workflow fits.
Review a report shape
Compare expectations against the sample report before assuming the audit will deliver automatic changes.
Approve next action
Move from findings to staging tests, rollout planning, or deeper investigation only after a human owner signs off.
Copyable brief
Use this request structure
Keep the first request short. The best first response usually confirms scope, not a final fix.
| Field | What to write |
|---|---|
| Symptom | Which workflow is slow, when it happens, and who is affected. |
| Environment | Database engine, version, hosting provider, approximate size, and critical tables if known. |
| Evidence | Slow query examples, EXPLAIN output, query stats, index list, table growth, or wait notes you can share safely. |
| Boundary | Read-only only, no production writes, no automatic index creation, and any data that cannot leave your environment. |
| Decision needed | Whether you need triage, a sample report expectation, a PostgreSQL specialist route, or a broader audit preparation step. |
Choose the next page
Review the read-only audit boundary when access is the concern. Review the sample report when deliverables are unclear. Use the FAQ for support scope and timing questions. PostgreSQL teams can continue to the PostgreSQL audit hub.