EC
02000
PostgreSQLWARNINGCriticalNo DataHIGH confidence

no data

What this means

SQLSTATE 02000 is raised when a SELECT INTO or FETCH statement returns no rows. In PL/pgSQL it can be tested via the FOUND variable. It does not abort the transaction but may indicate unexpected empty results.

Why it happens
  1. 1SELECT INTO or FETCH from a cursor returns zero rows
  2. 2A PL/pgSQL statement expected to return exactly one row returned none
How to reproduce

SELECT INTO in PL/pgSQL where no row matches the condition.

trigger — this will error
trigger — this will error
DO $
DECLARE v_name TEXT;
BEGIN
  SELECT name INTO v_name FROM users WHERE id = 999; -- no such row
  IF NOT FOUND THEN
    RAISE NOTICE 'No row found (SQLSTATE 02000)';
  END IF;
END $;

expected output

NOTICE:  No row found (SQLSTATE 02000)

Fix 1

Check FOUND after SELECT INTO

WHEN In PL/pgSQL when a row may or may not exist.

Check FOUND after SELECT INTO
IF NOT FOUND THEN
  -- handle missing row
END IF;

Why this works

The FOUND boolean is set to FALSE when SELECT INTO returns no rows, allowing graceful handling without exceptions.

Fix 2

Use SELECT INTO STRICT to raise an exception on no data

WHEN When the row is required and absence is a programming error.

Use SELECT INTO STRICT to raise an exception on no data
SELECT name INTO STRICT v_name FROM users WHERE id = p_id;

Why this works

STRICT raises NO_DATA_FOUND (02000) as an exception that must be caught, preventing silent mishandling.

What not to do

✕ Ignore the FOUND check after SELECT INTO

The variable retains its previous value when no row is found, leading to silent logic errors using stale data.

Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev

← All PostgreSQL errors