Re: BUG #18456: Trigger data in plpython3u trigger-function changes in AFTER UPDATE OR INSERT trigger

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #18456: Trigger data in plpython3u trigger-function changes in AFTER UPDATE OR INSERT trigger
Дата
Msg-id 2944262.1714847680@sss.pgh.pa.us
обсуждение исходный текст
Ответ на BUG #18456: Trigger data in plpython3u trigger-function changes in AFTER UPDATE OR INSERT trigger  (PG Bug reporting form <noreply@postgresql.org>)
Ответы Re: BUG #18456: Trigger data in plpython3u trigger-function changes in AFTER UPDATE OR INSERT trigger  (Jacques Combrink <jacques@quantsolutions.co.za>)
Список pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> Then the trigger data changes after the insert statement in the trigger
> function.

Hmm.  TD is defined as a global dictionary like SD, so it saves values
across calls to the plpython function.  So the inner INSERT operation
fires the same trigger, which decides not to print anything, but
nonetheless it's changed TD and the outer trigger call will see that.

There used to be similar problems in plain plpython functions if they
were invoked recursively, because named function arguments are also
passed as global variables.  We fixed that in a rather hacky way in
1d2fe56e4, ie save and restore those globals when recursing.
Probably the same thing could be done with TD.

            regards, tom lane



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

Предыдущее
От: Alena Rybakina
Дата:
Сообщение: Re: BUG #17257: (auto)vacuum hangs within lazy_scan_prune()
Следующее
От: David Rowley
Дата:
Сообщение: Re: BUG #18305: Unexpected error: "WindowFunc not found in subplan target lists" triggered by subqueries