PostgreSQL incident console
Fix your Postgres incident fast.
Paste the error, SQLSTATE, or log line. Get the cause, a fix that was reproduced on real PostgreSQL, and the exact diagnostics to run right now — cited to the manual, with no guesswork and no invented output.
The fix is always free. The full lab proof is Pro.
Every fix here was reproduced on real PostgreSQL 16 and captured verbatim — and the behavior applies across versions 14 to 18.
100
errors reproduced
24
SQLSTATE classes
85
full lab transcripts
100%
manual-cited
On every error page
The same four answers, every time
Not a wall of documentation — a consistent, paste-to-fix path for the moment something breaks.
01
What actually failed
The real cause in plain language — not a reworded copy of the docs.
02
A fix we ran
The fix executed in a lab and captured working, with the verbatim output. Never a guess.
03
Diagnostics for right now
The pg_stat_activity, pg_locks, and blocking-PID queries that pin down this exact failure.
04
Cited to the source
Every claim linked to the precise section of the official PostgreSQL manual.
Who it's for
One reference, junior to staff
The same evidence serves a first-week engineer clearing their first deadlock and a staff DBA reviewing a migration.
Clear a production error
Paste the code straight from your logs — 40P01, 40001, 53300 — and get the cause, the fix, and the queries that confirm the incident is actually resolved.
Start from a symptom →Understand why a change failed
A constraint, lock, or type error stopped your migration or query. See why it fired and the change that keeps it from reaching production next time.
Browse the errors →Know the why, not just the fix
The internals, configuration, and runbooks behind the errors — from your first deadlock to the questions staff and DBA interviews actually ask.
Open interview prep →Why trust it
We don't paraphrase the docs — we run it
The same pipeline runs behind every entry, so the evidence is real.
- 01Spin up a throwaway PostgreSQL instance and trigger the failure for real.
- 02Capture the raw psql output, the SQLSTATE, and the lock/PID state verbatim.
- 03Explain the cause and fix, and cite the exact section of the official manual.
Prioritized by real signal
We cover what actually breaks
The topics here are not guesses. They track what breaks in production — for example, the deadlock spike surfaced by the community incident feed at pgmoodring.com. Real signal in, reproduced evidence out.
Fighting an incident now? Start from the code and work back to the proof.
Free forever
Fix the incident
Every one of the 100 error explanations — the cause, the fix, the SQLSTATE reference, the glossary, and the GUC guide. Everything you need to get unblocked. No trial, no card.
Start readingPro · $24.99/mo or $199/yr
Get the proof
Unlock the full lab transcript behind each error: the exact reproduction SQL, the verbatim output, the live lock-graph and blocking-PID proofs, and the per-error SQLSTATE audit — the evidence, not just the summary.
Go ProEverything inside
Two ways in: firefight, or go deep
Reach for the top row when something is broken, the bottom when you have time to learn. Every page links to the terms, runbooks, and parameters it touches.
When you are firefighting
Error reference
100 SQLSTATEsEvery error's cause, fix, and diagnostics — each one reproduced in a real lab.
Includes: Deadlocks, serialization failures, unique & FK violations, lock timeouts
Symptom triage
GuidedNo error code to hand? Start from what you are seeing and narrow to the cause.
Includes: Transactions aborting, connections failing, constraints rejecting writes
Cookbook
70 runbooksOrdered steps for a live incident, ending in a query that confirms you are done.
Includes: Diagnose a live deadlock, cancel a runaway query, ship a lock-free migration
When you are learning
Internals lessons
36 lessonsHow PostgreSQL works under the hood — grounded in the source, re-run in a real lab. First 5 fully free; the rest free to read with 40 captured transcripts unlocked by Pro.
Includes: MVCC row versions, WAL, the planner, b-tree pages
Glossary
17 termsThe vocabulary behind incidents and internals, in plain language.
Includes: MVCC, write-ahead log, autovacuum, visibility map
GUC guide
6 parametersThe configuration parameters that actually move production behavior.
Includes: shared_buffers, work_mem, lock_timeout, deadlock_timeout
Learning pathways
2 tracksStructured routes from foundations to performance and operations.
Includes: PostgreSQL foundations, performance and planning
Interview prep
11 questionsThe Postgres questions senior and DBA interviews actually ask, with real answers.
Includes: REPEATABLE READ vs SERIALIZABLE, VACUUM and MVCC