Incident brief
CASE not found (no matching branch)
A PL/pgSQL CASE statement with no matching WHEN and no ELSE raises this at runtime when the selector matches none of the branches.
In 10 seconds
- What
- CASE not found (no matching branch)
- What triggers it
- Write a PL/pgSQL CASE statement whose WHEN branches do not cover the runtime value and omit an ELSE.
- The fix
- Add an ELSE branch (even ELSE NULL) so unmatched values are handled.
- Proof
- Reproduced on PostgreSQL 18.4 → A single DO block reproduces SQLSTATE 20000; a CASE with no matching WHEN and no ELSE fails at runtime with a hint.
The fix
What to do right now
The immediate, application-level response to this error.
- Add an ELSE branch (even ELSE NULL) so unmatched values are handled.
- Or ensure the WHEN branches exhaustively cover every possible value.
-- Add an ELSE branch so unmatched values are handled.
DO $$ BEGIN CASE 5 WHEN 1 THEN NULL; ELSE NULL; END CASE; END $$;Diagnose
See it live on the server
Run these against the affected instance to confirm the diagnosis before you act.
Standard triage — not specific to this error
These are canonical PostgreSQL system-catalog queries, shown as SQL to run. No sample output is attached because this is general triage, not a captured lab transcript.This SQLSTATE does not have an error-specific live snapshot yet. These are the canonical system-catalog queries you run against the affected server to see the problem in real time — standard triage, not a reproduced transcript.
What is running right now
Active backends, how long each has been running, and what it is waiting on.
SELECT pid,
state,
wait_event_type,
wait_event,
now() - query_start AS running_for,
left(query, 80) AS query
FROM pg_stat_activity
WHERE state <> 'idle'
AND pid <> pg_backend_pid()
ORDER BY running_for DESC NULLS LAST;Who is blocking whom
Turn raw blocking PIDs into the actual queries on both sides of the wait.
SELECT blocked.pid AS blocked_pid,
blocked.query AS blocked_query,
blocking.pid AS blocking_pid,
blocking.query AS blocking_query
FROM pg_stat_activity AS blocked
JOIN LATERAL unnest(pg_blocking_pids(blocked.pid)) AS b(pid) ON true
JOIN pg_stat_activity AS blocking ON blocking.pid = b.pid
WHERE cardinality(pg_blocking_pids(blocked.pid)) > 0;Locks that are still waiting
Every lock a backend has requested but not yet been granted.
SELECT l.pid,
l.locktype,
l.mode,
l.granted,
COALESCE(c.relname, l.transactionid::text) AS object
FROM pg_locks l
LEFT JOIN pg_class c ON c.oid = l.relation
WHERE NOT l.granted
ORDER BY l.pid;Why it happens
What PostgreSQL is telling you
The mechanism behind the error, grounded in the official manual — not paraphrased.
PostgreSQL 18 Documentation — Appendix A. PostgreSQL Error Codes (Table A.1, Class 20 — Case Not Found)
20000 → case_not_foundRead the full section on postgresql.org →
Running a CASE with no matching branch
No WHEN matched and there was no ELSE, so PL/pgSQL raises 'case not found' and hints that the ELSE part is missing.The session continues normally
The failing statement ran outside a transaction block, so nothing was left in a bad state — the next statement in the same connection runs normally.Reproduce & verify
A real, single-session PostgreSQL reproduction
A literal transcript of SQL run against a live PostgreSQL instance in an isolated lab — the commands below are exactly what was executed.
- 1Write a PL/pgSQL CASE statement whose WHEN branches do not cover the runtime value and omit an ELSE.
- 2At execution the selector matches no branch.
- 3PL/pgSQL raises SQLSTATE 20000 with a hint that the ELSE part is missing.
A status-handling function hit an unexpected value that none of its WHEN branches covered, and the missing ELSE turned it into a runtime error.
-- The error is self-contained in one statement; no schema is required.
SELECT 'no schema needed' AS setup_note;DO $$ BEGIN CASE 5 WHEN 1 THEN NULL; WHEN 2 THEN NULL; END CASE; END $$;SELECT 'ok' AS session_after_error;What PostgreSQL actually returned
setup_note
------------------
no schema needed
(1 row)ERROR: case not found
HINT: CASE statement is missing ELSE part.
CONTEXT: PL/pgSQL function inline_code_block line 1 at CASE session_after_error
---------------------
ok
(1 row)The same block runs cleanly once an ELSE branch handles unmatched values.
We add ELSE NULL and rerun the block to show it completes.
Without this
Before: an unmatched CASE aborts
With this, tested
After: ELSE NULL handles the value
What Pro unlocks here
- The exact prevention SQL — copy-paste ready
- Raw psql output captured from the Docker lab
- A senior-DBA action list to take it further
- Live monitoring queries to catch it in production
- The deeper audit: fix-that-fails counterexample, GUC before/after, server-log evidence
Related & next steps
Follow the thread
Everything this error touches — jump straight to the sibling error, term, runbook, or parameter.
Verification
- Last verified
- 2026-07-24 (isolated lab, PostgreSQL 18.4)
- Reviewed by
- Verified against PostgreSQL 18.4 in an isolated lab environment
- Audit status
- reviewed