Invalid Role Specification — SQLSTATE 0P000

SQLSTATE 0P000 condition invalid_role_specification class 0P — Invalid Role Specification 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 0P000 (invalid_role_specification), a condition in the Invalid Role Specification class.

  • The error is written to the server log and returned to the client carrying SQLSTATE 0P000.
  • 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 invalid_role_specification 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

0P000 belongs to Class 0P — Invalid Role Specification. In this class, the role specification is invalid.

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

3 Recovery & verify Free

Confirm the role exists and is spelled correctly; create it or correct the name.

Reference: PostgreSQL error codes — Class 0P (Invalid Role Specification).