babelfish-for-postgresql / babelfish_extensions / 12391492564

74%

BABEL_5_X_DEV: 77%

push

github

Fix transaction leak when DMLs contains a non pltsql language function which calls another non tsql function inside try catch (#3217) (#3273)

When DMLs are executed outside a user transaction block, babelfish starts an implicit transaction to handle errors inside triggers. This is done irrespective of whether the statement actually fires a trigger.
Now if the DML calls a non pltsql function which in calls another non tsql func or procedure inside a try catch, we do not properly decrement the pltsql_sys_func_entry_count variable properly. So the return value of pltsql_support_tsql_transactions() is different at beginning of the DML compared to after the end of the statement. This difference leads to babelfish not commit the implict transaction block.
As a fix, store the value of pltsql_support_tsql_transactions() at start of execution of DML and just reuse it for after execution.

Issues Resolved: [BABEL-5446]

Signed-off-by: Tanzeel Khan tzlkhan@amazon.com

9 of 9 new or added lines in 1 file covered. (100.0%)

43105 of 58423 relevant lines covered (73.78%)

147331.98 hits per line