-
- Downloads
Fix plpython's handling of functions used as triggers on multiple tables.
plpython tried to use a single cache entry for a trigger function, but it needs a separate cache entry for each table the trigger is applied to, because there is table-dependent data in there. This was done correctly before 9.1, but commit 46211da1 broke it by simplifying the lookup key from "function OID and triggered table OID" to "function OID and is-trigger boolean". Go back to using both OIDs as the lookup key. Per bug report from Sandro Santilli. Andres Freund
Showing
- src/pl/plpython/expected/plpython_trigger.out 24 additions, 0 deletionssrc/pl/plpython/expected/plpython_trigger.out
- src/pl/plpython/plpy_main.c 7 additions, 3 deletionssrc/pl/plpython/plpy_main.c
- src/pl/plpython/plpy_procedure.c 41 additions, 36 deletionssrc/pl/plpython/plpy_procedure.c
- src/pl/plpython/plpy_procedure.h 9 additions, 2 deletionssrc/pl/plpython/plpy_procedure.h
- src/pl/plpython/sql/plpython_trigger.sql 18 additions, 0 deletionssrc/pl/plpython/sql/plpython_trigger.sql
Loading
Please register or sign in to comment