SQLSTATE 0P000 ERROR Class 0P: Invalid Role Specification

invalid_role_specification Invalid Role Specification — SQLSTATE 0P000

SQLSTATE 0P000 (invalid_role_specification): The role specification is invalid.

PG 12, 13, 14, 15, 16, 17, 18 Official docs
Last reviewed May 2025 Grounded in source

Symptoms

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.

Environment

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

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.

Diagnostic Queries

Recovery

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

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

Was this helpful?