babelfish-for-postgresql / babelfish_extensions / 10058794655

76%

BABEL_5_X_DEV: 77%

Build Type

push

github

Committed by web-flow

Commit Message

Fix error when OUTPUT INTO table variable statement fires trigger (#2639)

Fix error portal snapshots (1) did not account for all active snapshots (2) when OUTPUT INTO table variable statement fires triggers.

pltsql statements that could fire trigger must always run inside a transaction block. If a txn block is not active, we create one. We exclude some types of statements from this, one of them being DML on table variables since they can never fire a trigger. We detect this using the variable mod_stmt_tablevar.

Now an edge case here is OUTPUT into table variable stmt. Which we internally transform into two DML nodes.
TOP INSERT NODE (signifies the output into clause)
Another DELETE / UPDATE / INSERT node inside the top insert node -> with clause (specifies the first part of the output into clause )
As a fix we simply skip transaction commands inside pltsql UDFs and not rely on mod_stmt_tablevar on anymore.

Also blocked certain cases of OUTPUT clause which should not be allowed inside pltsql UDFs.

    OUTPUT clause flushes results to client (INTO clause is missing)
    OUTPUT INTO clause has a non local object as its target. (UDFs only allow DML on local objects)

Issues Resolved: BABEL-4859

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

Run Details

11 of 11 new or added lines in 2 files covered. (100.0%)

2 existing lines in 1 file now uncovered.

42903 of 58597 relevant lines covered (73.22%)

114262.88 hits per line