SQLSTATE 2D000 ERROR Class 2D: Invalid Transaction Termination

invalid_transaction_termination Invalid Transaction Termination — SQLSTATE 2D000

SQLSTATE 2D000 (invalid_transaction_termination): The transaction termination is invalid.

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

Symptoms

The server reports SQLSTATE 2D000 (invalid_transaction_termination), a condition in the Invalid Transaction Termination class.

  • The error is written to the server log and returned to the client carrying SQLSTATE 2D000.
  • 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_transaction_termination 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

2D000 belongs to Class 2D — Invalid Transaction Termination. In this class, the transaction termination is invalid.

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

Diagnostic Queries

Recovery

Do not COMMIT or ROLLBACK in a context that forbids it (for example inside certain functions); restructure the control flow.

Reference: PostgreSQL error codes — Class 2D (Invalid Transaction Termination).

Was this helpful?