Community Forum
Database Incident Forum Template
Ask database incident questions with read-only evidence for sessions, locks, slow queries, storage, cache and timestamps. It helps developers ask better questions, preserve useful evidence and keep public examples safe enough to share.
Use this when
- You want another developer to understand the issue without guessing.
- You need to remove secrets and private data before sharing evidence.
- You want the final answer to become a reusable Formalint-style reference.
Practical workflow
| Step | What to include |
|---|---|
| Start read-only | Use safe diagnostic SQL and avoid destructive fixes while the incident is unclear. |
| Capture time windows | Database symptoms need timestamps to match API logs, jobs and user reports. |
| Separate query from host | Slow pages can come from SQL, connection pools, disk IO, Redis or network pressure. |
| Share only safe samples | Hash IDs, remove customer data and redact connection strings. |
Template
Database:
Version:
Symptom window:
Read-only checks:
Slow query sample:
Lock/session evidence:
Recent deployment:Safety checklist
- Remove passwords, tokens, cookies, private keys and connection strings.
- Replace customer records with tiny synthetic examples.
- Keep exact error text, versions, command output and timestamps when safe.
- Say what changed after the fix so the answer helps future readers.
Good forum content is not long by default. It is specific, safe, reproducible and useful after the first reader leaves.
Related Formalint references
Continue with Postgresql Dba Checklist, Mysql Slow Query Debugging Guide, Formalint Developer Forum.