Symptoms
The server reports SQLSTATE 44000 (with_check_option_violation), a condition in the WITH CHECK OPTION Violation class.
- The error is written to the server log and returned to the client carrying
SQLSTATE 44000. - 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 with_check_option_violation 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
44000 belongs to Class 44 — WITH CHECK OPTION Violation. In this class, a row would violate a view's WITH CHECK OPTION.
The first two characters (44) identify the error class, so application code can match the whole class via 44000 when the specific code is not needed.
Diagnostic Queries
Recovery
Adjust the data so the row still satisfies the view definition, or change the view/option.
Reference: PostgreSQL error codes — Class 44 (WITH CHECK OPTION Violation).
Thanks — noted. This helps keep the database accurate.