Database processing after a lock condition

A system, comprising:

• a memory;
• and
• at least one processor coupled to the memory and configured to:
• receive a release of a lock on data of a database, wherein the lock on the data was provided to a first transaction responsive to a first request to access the data, wherein one or more queued transactions are waiting in a lock queue to access the data;
• associate, prior to the lock, a snapshot of the data with a second transaction;
• determine whether the data was modified by processing of the first transaction associated with the first request based on whether a flag was set prior to the receiving the release of the lock;
• provide the lock to the second transaction, from the lock queue, associated with a second request to access the data;
• determine that the flag was set prior to receiving the release of the lock;
• and
• refresh the snapshot of the data associated with the second transaction prior to an execution of the second transaction and based on a snapshot isolation level.

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

• receiving a release of a lock on data of a database, wherein the lock on the data was provided to a first transaction responsive to a first request to access the data, wherein one or more queued transactions are waiting in a lock queue to access the data;
• associating, prior to the lock, a snapshot of the data with a second transaction;
• determining whether the data was modified by processing of the first transaction associated with the first request based on whether a flag was set prior to the receiving the release of the lock;
• providing the lock to the second transaction, from the lock queue, associated with a second request to access the data;
• determining that the flag was set prior to receiving the release of the lock;
• and
• refreshing the snapshot of the data associated with the second transaction prior to an execution of the second transaction and based on a snapshot isolation level.