Method and system for lock after qualification for update queries

A non-transitory computer-readable device having instructions thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:

• generating a qualified timestamp corresponding to execution of a first operation of a first transaction over a table of a database, wherein the instructions thereon for generating the qualified timestamp comprises instructions for generating the qualified timestamp based at least in part on one or more of:
• a total CPU time for database requests that had a conflict on at least one row and had to wait for row lock,
• a number of database requests executed where a database request had a conflict on at least one row and had to wait for row lock,
• a total CPU time used by database requests that completed successfully without any conflicts from concurrent queries, or
• a total quantity of queries that ran with an index of the row of the table as read cursor successfully without any conflicts from concurrent queries;
• determining, based on the qualified timestamp, that a row of the table is not locked by a second operation of a second transaction over the database;
• determining that the row meets a condition of the first operation;
• and
• updating, based on the qualified timestamp, the row in response to the row meeting the condition, the updating including acquiring a lock on the row of the table.

A system comprising:

• a memory storing instructions thereon;
• and
• at least one processor coupled with the memory and configured by the instructions to:
• generate a qualified timestamp corresponding to execution of a first operation of a first transaction over a table of a database, wherein to generate the qualified timestamp the at least one processor is configured to generate the qualified timestamp based at least in part on one or more of:
• a total CPU time for database requests that had a conflict on at least one row and had to wait for row lock,
• a number of database requests executed where a database request had a conflict on at least one row and had to wait for row lock,
• a total CPU time used by database requests that completed successfully without any conflicts from concurrent queries, or
• a total quantity of queries that ran with an index of the row of the table as read cursor successfully without any conflicts from concurrent queries:
• determine, based on the qualified timestamp, that a row of the table is not locked by a second operation of a second transaction over the database;
• determine that the row meets a condition of the first operation;
• and
• update, based on the qualified timestamp, the row in response to the row meeting the condition, the updating including acquiring a lock on the row of the table.