Evidence-first PostgreSQL reference

The PostgreSQL error reference that shows its work.

Most references paraphrase the docs. We run it — every error here was reproduced in an isolated PostgreSQL lab, so you get the exact SQL, the raw psql output, and the fix, cited back to the official manual. No hand-waving, no fabricated logs.

The fix is always free. The depth is Pro.

56

errors reproduced

18

SQLSTATE classes

41

full lab transcripts

100%

manual-cited

Free forever

Understand any error

Every one of the 56 error explanations, the SQLSTATE reference, the glossary, and the GUC guide — the full picture of what went wrong and how to fix it. No trial, no card.

Start reading

Pro · $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 Pro

How every page is built

Reproduce → capture → cite

The same pipeline runs behind every entry, so the evidence is real.

  1. 01Spin up a throwaway PostgreSQL instance and trigger the failure for real.
  2. 02Capture the raw psql output, the SQLSTATE, and the lock/PID state verbatim.
  3. 03Explain the cause and fix, and cite the exact section of the official manual.

Why it exists

Prioritized by real incident signal

The topics here aren't guesses. They track what actually breaks in production — for example, the deadlock spike surfaced by the community incident feed at pgmoodring.com. Real signal in, reproduced evidence out.

If you're fighting a PostgreSQL incident, start from the code and work back to the proof.

Open the SQLSTATE index

Everything inside

One connected reference

Errors link to the terms, runbooks, and parameters they touch — so you can follow an incident all the way down.