Native transaction guard

One or more non-transitory computer-readable media storing a set of instructions, wherein the set of instructions includes instructions, which when executed by one or more hardware processors, cause:

• receiving, by a database management system (DBMS), a first set of commands of a first transaction for execution in a first session of the DBMS with a first client and a second set of commands of a second transaction for execution in a second session of the DBMS with a second client;
• wherein the execution in the first session of the first set of commands causes the DBMS to generate a first transaction identifier that uniquely identifies the first transaction in the DBMS and is valid during a lifecycle of the first transaction;
• determining that the first transaction is a top-level transaction type, wherein a request to commit the first transaction is sent to the DBMS, separately from the first set of commands to be committed within the first transaction;
• wherein the execution in the second session of the second set of commands causes the DBMS to generate a second identifier that uniquely identifies the second transaction in the DBMS and is valid during a lifecycle of the second transaction;
• determining that the second transaction is a non-top-level transaction type;
• based, at least in part, on a) the determining that the first transaction is a top-level transaction type, and b) the determining that the second transaction is a non-toplevel transaction type, modifying a logical transaction history table of the DBMS with a commit outcome of the second transaction without modifying the logical transaction history table of the DBMS with transaction information of the first transaction;
• in response to receiving the first transaction identifier from the first client, determining a commit outcome of the first transaction.