Locator Exception — SQLSTATE 0F000

SQLSTATE 0F000 condition locator_exception class 0F — Locator Exception severity ERROR
Reproduced & verified on PostgreSQL 14.23, 15.18, 16.14, 17.10 and 18.4 — identical message on every version.
Last reviewed 29 May 2025 · Reproduced live with the SQL on this page.

! Symptoms Free

The server reports SQLSTATE 0F000 (locator_exception), a condition in the Locator Exception class.

  • The error is written to the server log and returned to the client carrying SQLSTATE 0F000.
  • Any driver (libpq, JDBC, psycopg, npgsql, pgx) surfaces this code in its error object so you can branch on it programmatically.
  • PL/pgSQL can trap it by name: EXCEPTION WHEN locator_exception THEN.

1 Environment & reproduce Free

Severity: ERROR  |  PostgreSQL versions: 12, 13, 14, 15, 16, 17

Reproduce with the exact statement and read the full message in the server log (raise log_min_messages / set log_min_error_statement for more context).

? Root cause Free

0F000 belongs to Class 0F — Locator Exception. In this class, a large-object locator is invalid.

The first two characters (0F) identify the error class, so application code can match the whole class via 0F000 when the specific code is not needed.

3 Recovery & verify Free

Ensure the large-object handle is open and valid for the current transaction before using it.

Reference: PostgreSQL error codes — Class 0F (Locator Exception).