Report the trigger name when complaining about "tuple to be updated was already modified by an operation triggered by the current command"?

From: Joe Van Dyk <joe(at)tanga(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Report the trigger name when complaining about "tuple to be updated was already modified by an operation triggered by the current command"?
Date: 2013-10-21 17:59:30
Message-ID: CACfv+pLcKiQjVuovy+viSYQmPikuWPQubp7c66SFO5urtgXZQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I started getting this error after upgrading from 9.2.4 to 9.3.1:

ERROR: tuple to be updated was already modified by an operation triggered
by the current command
HINT: Consider using an AFTER trigger instead of a BEFORE trigger to
propagate changes to other rows.
STATEMENT: DELETE FROM "channels_products" WHERE
"channels_products"."product_id" = 53 AND "channels_products"."channel_id"
IN (18, 24, 26, 53, 57, 76, 88)

This was the complete entry in the log. There was no mention about what
trigger or function caused the problem. Can there be?

(I fixed the error by moving the before trigger to an after one.)

Joe

Browse pgsql-general by date

  From Date Subject
Next Message David Johnston 2013-10-21 18:01:04 Re: Bug? Function with side effects not evaluated in CTE
Previous Message ramistuni 2013-10-21 17:57:42 Upgrade from 9.1 to 9.10