How to fix Trigger protocol violated in PostgreSQL

PostgreSQLINTERMEDIATEMEDIUMUpdated Dec 29, 2025· 107 views

PostgreSQL error 39P01 "Trigger protocol violated" occurs when a trigger function does not return the correct value type or structure. BEFORE triggers must return NULL or a row matching the table structure; AFTER triggers must also return a value. Ensure your trigger function is properly defined with the TRIGGER return type.

Quick fix

Fixes 39P01

CREATE OR REPLACE FUNCTION my_trigger_func()
RETURNS TRIGGER AS $$
BEGIN
  -- trigger logic here
END;
$$ LANGUAGE plpgsql;
  1. Verify the trigger function return type
  2. For BEFORE triggers, ensure proper RETURN statement
  3. For AFTER triggers, include a RETURN statement
  4. Verify the trigger is created correctly
postgresql — error
CREATE OR REPLACE FUNCTION my_trigger_func()
RETURNS TRIGGER AS $$
BEGIN
  -- trigger logic here
END;
$$ LANGUAGE plpgsql;
Trigger protocol violated

What this error means

Error 39P01 indicates that a trigger function has violated PostgreSQL's trigger protocol by returning an invalid value or having an incorrect function signature. Trigger functions in PostgreSQL must follow strict rules: they must be declared with a TRIGGER return type, and BEFORE row-level triggers must return either NULL (to skip the operation) or NEW/OLD (a row matching the table structure). AFTER triggers should also return a value, though it is typically ignored. When a trigger function fails to meet these requirements, PostgreSQL raises error 39P01 to prevent unpredictable behavior or data corruption.

Typical symptoms

  • Trigger function fails to execute with "protocol violated" error
  • INSERT, UPDATE, or DELETE operations fail when triggers are defined on the table
  • Trigger returns wrong data type or incomplete row structure
  • Error occurs only when a specific trigger is active
  • Disabling the trigger allows the operation to succeed

Common causes

  1. Trigger function does not have a TRIGGER return type declaration
  2. BEFORE row-level trigger does not return NEW (for INSERT/UPDATE) or OLD (for DELETE), or NULL
  3. Trigger function returns a value that does not match the table's row structure
  4. Trigger function is written in the wrong procedural language or missing required syntax
  5. Function signature mismatch—trigger functions must accept RECORD and TRIGGER as implicit parameters

How to fix "Trigger protocol violated"

1Verify the trigger function return type

Check that your trigger function is declared with RETURNS TRIGGER. For example:

sql
CREATE OR REPLACE FUNCTION my_trigger_func()
RETURNS TRIGGER AS $$
BEGIN
  -- trigger logic here
END;
$$ LANGUAGE plpgsql;

The RETURNS TRIGGER keyword is required for all trigger functions.

2For BEFORE triggers, ensure proper RETURN statement

BEFORE row-level triggers must return NEW (for INSERT/UPDATE), OLD (for DELETE), or NULL:

sql
CREATE OR REPLACE FUNCTION before_update_func()
RETURNS TRIGGER AS $$
BEGIN
  NEW.updated_at = NOW();
  RETURN NEW;  -- Must return NEW for BEFORE INSERT/UPDATE
END;
$$ LANGUAGE plpgsql;

Returning NULL will skip the operation (useful for validation). Returning the row continues the operation with any modified values.

3For AFTER triggers, include a RETURN statement

Even though AFTER triggers ignore the return value, you must still include a RETURN statement:

sql
CREATE OR REPLACE FUNCTION after_insert_func()
RETURNS TRIGGER AS $$
BEGIN
  INSERT INTO audit_log (action, record_id) VALUES ('INSERT', NEW.id);
  RETURN NEW;  -- Required even for AFTER triggers
END;
$$ LANGUAGE plpgsql;
4Verify the trigger is created correctly

Ensure the trigger references the function with the correct syntax:

sql
CREATE TRIGGER my_table_before_update
BEFORE UPDATE ON my_table
FOR EACH ROW
EXECUTE FUNCTION before_update_func();

For row-level triggers on BEFORE events, use FOR EACH ROW. Statement-level triggers use FOR EACH STATEMENT.

5Test the trigger with a simple operation

After fixing the function, test it with a basic insert, update, or delete:

sql
INSERT INTO my_table (name) VALUES ('test');

If the error persists, check the PostgreSQL server logs for more details:

sql
SELECT pg_current_logfile();

View the log file to see the exact error message from the trigger function.

Advanced notes

Trigger protocol violations can also occur when using procedural languages other than PL/pgSQL (like PL/Python or PL/Perl), which have different conventions for returning values. If using these languages, ensure the return value is explicitly constructed to match PostgreSQL's trigger protocol. Additionally, some ORMs and database libraries may have issues when AFTER triggers are defined on tables with insert/update operations. If disabling the trigger resolves the issue, the problem is with the trigger function itself, not the application. For complex triggers, consider testing the function in isolation using SELECT to verify its output type and structure before attaching it to the trigger.

Frequently asked questions

What does "39P01" mean?
Error 39P01 indicates that a trigger function has violated PostgreSQL's trigger protocol by returning an invalid value or having an incorrect function signature. Trigger functions in PostgreSQL must follow strict rules: they must be declared with a TRIGGER return type, and BEFORE row-level triggers must return either NULL (to skip the operation) or NEW/OLD (a row matching the table structure). AFTER triggers should also return a value, though it is typically ignored.
How do I fix "39P01"?
PostgreSQL error 39P01 "Trigger protocol violated" occurs when a trigger function does not return the correct value type or structure. BEFORE triggers must return NULL or a row matching the table structure; AFTER triggers must also return a value. Ensure your trigger function is properly defined with the TRIGGER return type.
What causes "39P01"?
Trigger function does not have a TRIGGER return type declaration BEFORE row-level trigger does not return NEW (for INSERT/UPDATE) or OLD (for DELETE), or NULL Trigger function returns a value that does not match the table's row structure
Is the "39P01" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading