Re: BUG #18456: Trigger data in plpython3u trigger-function changes in AFTER UPDATE OR INSERT trigger - Mailing list pgsql-bugs
Okay thanks for confirming.
Is there something that I can do to get this issue on a list to be fixed, or is this report enough?
Sorry for the questions, first time posting here, not sure how everything works.
Regards
| ||||||||||||||||||||||||||||||||||||||||||||
On Sat, May 4, 2024 at 8:34 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
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 by date: