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

Поиск
Список
Период
Сортировка
От Joe Van Dyk
Тема Report the trigger name when complaining about "tuple to be updated was already modified by an operation triggered by the current command"?
Дата
Msg-id CACfv+pLcKiQjVuovy+viSYQmPikuWPQubp7c66SFO5urtgXZQw@mail.gmail.com
обсуждение исходный текст
Список 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

В списке pgsql-general по дате отправления:

Предыдущее
От: ramistuni
Дата:
Сообщение: Upgrade from 9.1 to 9.10
Следующее
От: David Johnston
Дата:
Сообщение: Re: Bug? Function with side effects not evaluated in CTE