Predictive concurrency control protocol and system thereof

A method for managing the execution of database transactions, comprising:

• receiving at least one statement that is a part of a transaction, wherein the transaction is initiated by a client to be executed on a database system;
• executing tasks included in each of the at least one received statements in an optimistic manner, wherein the received at least one statement is not a commit statement;
• upon receiving a commit statement, validating the transaction in a predictive and pessimistic manner to determine if the transaction can be committed before any conflicting transaction;
• and
• returning to the client an acknowledgment that the transaction is committed, where the transaction is not dependent on any conflicting transaction.

A non-transitory computer-readable medium storing a set of instructions for managing the execution of database transactions in a database system, the set of instructions comprising:

• one or more instructions that, when executed by one or more processors of a device, cause the device to:
• during a validation phase of a transaction, identifying conditional conflicts and their corresponding conflicting transactions, wherein the corresponding conflicting transactions are reading-transactions conflicting with the transaction;
• for each conditional conflict, classify its state to determine if the transaction can commit, with respect to the conditional conflict, before the corresponding conflicting transaction;
• mark the transaction as dependent on the corresponding conflicting transaction when the transaction cannot commit before the corresponding conflicting transaction;
• and
• place a commit pause on data cells modified by the transaction, thereby allowing the transaction to commit, when the transaction can commit before any corresponding conflicting transactions.

A system for managing the execution of database transactions in a database system comprising:

• one or more processors configured to:
• during a validation phase of a transaction, identifying conditional conflicts and their corresponding conflicting transactions, wherein the corresponding conflicting transactions are reading-transactions conflicting with the transaction;
• for each conditional conflict, classify its state to determine if the transaction can commit, with respect to the conditional conflict, before the corresponding conflicting transaction;
• mark the transaction as dependent on the corresponding conflicting transaction when the transaction cannot commit before the corresponding conflicting transaction;
• and
• place a commit pause on data cells modified by the transaction, thereby allowing the transaction to commit, when the transaction can commit before any corresponding conflicting transactions.

A database system, comprising:

• a plurality of nodes, wherein each of the plurality of nodes include:
• a storage;
• and
• one or more processors, wherein the one or more processors configured to:
• receive at least one statement that is a part of a transaction, wherein the transaction is initiated by a client to be executed on a database system;
• execute tasks included in each of the at least one received statements in an optimistic manner, wherein the received at least one statement is not a commit statement;
• upon receiving a commit statement, validate the transaction in a predictive and pessimistic manner to determine if the transaction can be committed before any conflicting transaction;
• and
• return to the client an acknowledgment that the transaction is committed, where the transaction is not dependent on any conflicting transaction.