triggered_data_change_violation Triggered Data Change Violation — SQLSTATE 27000

The server reports SQLSTATE 27000 (triggered_data_change_violation), a condition in the Triggered Data Change Violation class.

• The error is written to the server log and returned to the client carrying SQLSTATE 27000.
• 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 triggered_data_change_violation THEN.

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).

27000 belongs to Class 27 — Triggered Data Change Violation. In this class, a trigger attempted an illegal data change.

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

Review the trigger that modified the row; it changed data in a way the statement does not allow.

Reference: PostgreSQL error codes — Class 27 (Triggered Data Change Violation).