Granted Patent B2

US 12,436,943 · App. 18/431,285 · Granted Oct 7, 2025

Inventors: Erez Webman (Petach Tikva, IL); Irit Yadin-Lempel (Caesarea, IL); Eran Borovik (Zikhron Ya'akov, IL); Hilla Atzmon (Haifa, IL)

Assignee: Regatta Data Ltd.

G06F16/2379G06F16/215G06F16/27

Abstract

Claims (144)

1. A method for managing execution of database transactions by facilitating point-in-time image (PiT), comprising:

receiving at least one statement being part of a transaction, wherein the transaction is initiated by a client to be executed on a distributed database system;

sending a single request to a sequencer server (SEQ-server) to create at least one PiT, wherein the SEQ-server provides a logical timestamp counter (LTC) value as a timestamp of the PiT;

upon creation of the at least one PiT, causing execution of the at least one statement, wherein a PiT provides a state and content of committed data in the distributed database system;

upon receiving a commit statement, performing a commitment process of the transaction, wherein the commitment process is based on a commitment timestamp (CMTS) set by the SEQ-server based on an incremented value of the LTC; and

returning an acknowledgment of the transaction commitment to the client.

2. The method of claim 1 , initiating the creation of the at least one PiT further comprises:

receiving the single PiT creation request from an SEQ-agent, wherein the PiT creation request is initiated by a transaction manager executing the transaction;

upon receiving of the creation request, incrementing the LTC value; and

sending the incremented LTC value to the SEQ-agent as a PiT timestamp, wherein the PiT timestamp is returned to the transaction manager.

3. The method of claim 1 , wherein initiating the creation of the at least one PiT further comprises:

receiving a PiT creation request from an SEQ-agent, wherein the PiT creation request is initiated by a transaction manager executing the transaction;

queuing the received PiT request in the SEQ-server;

upon satisfying a PiT creation rule, incrementing the LTC value; and

sending the incremented LTC value to the SEQ-agent as a PiT timestamp, wherein the PiT timestamp is returned to the transaction manager.

4. The method of claim 3 , further comprising:

receiving a plurality of PiT creation requests from a plurality of SEQ-agents; and

for each queued PiT creation request, sending a response with the incremented LTC value to a respective SEQ-agent as the PiT timestamp.

5. The method of claim 4 , wherein the PiT creation rule includes any one of: a predetermined number of PiT creation requests, a predetermined time window, or both.

6. The method of claim 1 , wherein initiating the creation of the at least one PiT further comprises:

receiving a PiT creation request at an SEQ-agent, wherein the PiT creation request is initiated by a transaction manager executing the transaction;

queuing the received PiT request in the SEQ-agent;

upon satisfying a SEQ-agent-side PiT creation rule, sending a single unified PiT creation request to the SEQ-server to create a unified PiT for all requests queued in the SEQ-agent; and

receiving the incremented LTC value as a unified PiT timestamp, wherein the unified PiT timestamp is returned to the transaction manager.

7. The method of claim 6 , further comprising:

receiving a plurality of PiT creation requests from a plurality of transaction managers; and

for each queued PiT creation request, sending a response with the unified PiT timestamp to a respective transaction manager.

8. The method of claim 7 , further comprising:

queuing the unified PiT creation request in the SEQ-server; and

upon satisfying a SEQ-server-side PiT creation rule, incrementing the LTC value, thereby creating a unified PiT timestamp, wherein the created unified PiT timestamp serves multiple unified PiT creation requests sent by a plurality of SEQ-agents.

9. The method of claim 8 , the SEQ-server-side PiT creation rule includes any one of: a predetermined number of PiT creation requests, a predetermined time window, or both, wherein the SEQ-server-side PiT creation rule is triggered when a first transaction manager of the plurality of transaction managers calls the SEQ-agent.

10. The method of claim 1 , further comprising:

generating the CMTS based on the incremented value of the LTC.

11. The method of claim 10 , further comprising:

receiving a CMTS creation request from an SEQ-agent, wherein the CMTS creation request is initiated by a transaction manager executing the transaction;

upon reception of the creation request, incrementing the LTC value; and

sending the incremented LTC value to the SEQ-agent as the CMTS, wherein the CMTS is returned to the transaction manager.

12. The method of claim 10 , further comprising:

receiving a CMTS creation request at an SEQ-agent, wherein the CMTS creation request is initiated by a transaction manager executing the transaction;

queuing the received CMTS request in the SEQ-agent;

counting the queued CMTS requests;

upon satisfying a CMTS creation rule, sending a single CMTS creation request, wherein the single CMTS creation request specifies a number of queued CMTS requests; and

receiving a range of LTC values as CMTSs.

13. The method of claim 12 , further comprising:

receiving a plurality of CMTS creation requests from a plurality of transaction managers; and

for each queued CMTS creation request, sending a response to a respective transaction manager with a CMTS from the received CMTSs, wherein each of the plurality of transaction managers receives a different CMTS.

14. The method of claim 12 , wherein the CMTS creation rule includes any one of: a predetermined number of CMTS creation requests, a predetermined time window, or both.

15. The method of claim 1 , wherein performing the commitment process of the transaction further comprises:

placing a commit pause on each data cell modified by the transaction;

obtaining the CMTS;

sending a commit completion message to a transaction agent that participated in the execution of the transaction; and

causing the transaction agent to commit row-versions and release any commit pause.

16. The method of claim 1 , wherein causing the execution of the at least one statement further comprises performing any one of: a write operation and a read operation.

17. The method of claim 16 , wherein performing the read operation further comprises:

reading data from at least the created PiT.

18. The method of claim 16 , wherein performing the read operation further comprises:

when data has changed after the creation of the PiT, reading data from at least a latest committed row-version.

19. The method of claim 16 , wherein performing the write operation further comprises:

writing data to at least one data cell in an uncommitted manner.

20. The method of claim 1 , wherein the distributed database system comprises: one SEQ-server and a plurality of SEQ-agents executed on a plurality of nodes of the distributed database system, wherein each of the plurality of nodes incudes a storage implementing a persistent data-layout that allows multi-version data-cells.

21. The method of claim 20 , wherein the plurality of SEQ-agents are configured at a predefined hierarchy.

22. A system for managing execution of database transactions by facilitating point-in-time image (PiT) comprising:

one or more processors configured to:

receive at least one statement being part of a transaction, wherein the transaction is initiated by a client to be executed on a distributed database system;

send a single request to a sequencer server (SEQ-server) to create at least one PiT, wherein the SEQ-server provides a logical timestamp counter (LTC) value as a timestamp of the PiT;

upon creation of the at least one PiT, cause execution of the at least one statement, wherein a PiT provides a state and content of committed data in the distributed database system;

upon receiving a commit statement, perform a commitment process of the transaction, wherein the commitment process is based on a commitment timestamp (CMTS) set by the SEQ-server based on an incremented value of the LTC; and

return an acknowledgment of the transaction commitment to the client.

23. The system of claim 22 , wherein the one or more processors are further configured to:

initiate the creation of the at least one PiT further comprises:

receive the single PiT creation request from an SEQ-agent, wherein the PiT creation request is initiated by a transaction manager executing the transaction;

upon receiving of the creation request, increment the LTC value; and

send the incremented LTC value to the SEQ-agent as a PiT timestamp, wherein the PiT timestamp is returned to the transaction manager.

24. The system of claim 22 , wherein the one or more processors, when initiating the creation of the at least one PiT, are configured to:

receive a PiT creation request from an SEQ-agent, wherein the PiT creation request is initiated by a transaction manager executing the transaction;

queue the received PiT request in the SEQ-server;

upon satisfying a PiT creation rule, increment the LTC value; and

send the incremented LTC value to the SEQ-agent as a PiT timestamp, wherein the PiT timestamp is returned to the transaction manager.

25. The system of claim 24 , wherein the one or more processors are further configured to:

receive a plurality of PiT creation requests from a plurality of SEQ-agents; and

for each queued PiT creation request, send a response with the incremented LTC value to a respective SEQ-agent as the PIT timestamp.

26. The system of claim 25 , wherein the PiT creation rule includes any one of:

a predetermined number of PiT creation requests, a predetermined time window, or both.

27. The system of claim 22 , wherein the one or more processors, when initiating the creation of the at least one PiT, are configured to:

receive a PiT creation request at an SEQ-agent, wherein the PiT creation request is initiated by a transaction manager executing the transaction;

queue the received PiT request in the SEQ-agent;

upon satisfying a SEQ-agent-side PiT creation rule, send a single unified PiT creation request to the SEQ-server to create a unified PiT for all requests queued in the SEQ-agent; and

receive the incremented LTC value as a unified PiT timestamp, wherein the unified PiT timestamp is returned to the transaction manager.

28. The system of claim 27 , wherein the one or more processors are further configured to:

receive a plurality of PiT creation requests from a plurality of transaction managers; and

for each queued PiT creation request, send a response with the unified PiT timestamp to a respective transaction manager.

29. The system of claim 28 , wherein the one or more processors are further configured to:

queue the unified PiT creation request in the SEQ-server; and

upon satisfying a SEQ-server-side PiT creation rule, increment the LTC value, thereby creating a unified PiT timestamp, wherein the created unified PiT timestamp serves multiple unified PiT creation requests sent by a plurality of SEQ-agents.

30. The system of claim 29 , the SEQ-server-side PiT creation rule includes any one of:

a predetermined number of PiT creation requests, a predetermined time window, or both, wherein the SEQ-server-side PiT creation rule is triggered when a first transaction manager of the plurality of transaction managers calls the SEQ-agent.

31. The system of claim 22 , wherein the one or more processors are further configured to:

generate the CMTS based on the incremented value of the LTC.

32. The system of claim 31 , wherein the one or more processors are further configured to:

receive a CMTS creation request from an SEQ-agent, wherein the CMTS creation request is initiated by a transaction manager executing the transaction;

upon reception of the creation request, increment the LTC value; and

send the incremented LTC value to the SEQ-agent as the CMTS, wherein the CMTS is returned to the transaction manager.

33. The system of claim 31 , wherein the one or more processors are further configured to:

receive a CMTS creation request at an SEQ-agent, wherein the CMTS creation request is initiated by a transaction manager executing the transaction;

queue the received CMTS request in the SEQ-agent;

count the queued CMTS requests;

upon satisfying a CMTS creation rule, send a single CMTS creation request, wherein the single CMTS creation request specifies a number of queued CMTS requests; and

receive a range of LTC values as CMTSs.

34. The system of claim 33 , wherein the one or more processors are further configured to:

receive a plurality of CMTS creation requests from a plurality of transaction managers; and

for each queued CMTS creation request, send a response to a respective transaction manager with a CMTS from the received CMTSs, wherein each of the plurality of transaction managers receives a different CMTS.

35. The system of claim 33 , wherein the CMTS creation rule includes any one of: a predetermined number of CMTS creation requests, a predetermined time window, or both.

36. The system of claim 22 , wherein the one or more processors, when performing the commitment process of the transaction, are configured to:

place a commit pause on each data cell modified by the transaction;

obtain the CMTS;

send a commit completion message to a transaction agent that participated in the execution of the transaction; and

cause the transaction agent to commit row-versions and release any commit pause.

37. The system of claim 22 , wherein the one or more processors are configured to execute the at least one statement performing any one of a write operation and a read operation.

38. The system of claim 37 , wherein the one or more processors, when performing the read operation, are configured to:

read data from at least the created PiT.

39. The system of claim 37 , wherein the one or more processors, when performing the read operation, are configured to:

when data has changed after the creation of the PiT, read data from at least a latest committed row-version.

40. The system of claim 37 , wherein the one or more processors, when performing the write operation, are configured to:

write data to at least one data cell in an uncommitted manner.

41. The system of claim 22 , wherein the distributed database system comprises: one SEQ-server and a plurality of SEQ-agents executed on a plurality of nodes of the distributed database system, wherein each of the plurality of nodes incudes a storage implementing a persistent data-layout that allows multi-version data-cells.

42. The system of claim 41 , wherein the plurality of SEQ-agents are configured at a predefined hierarchy.

43. A distributed database system comprises:

a plurality of nodes, wherein each of the plurality of nodes incudes a storage implementing a persistent data-layout that allows multi-version data-cells and one or more processors;

one sequencer server (SEQ-server); and

a plurality of SEQ-agents executed on a plurality of nodes of the distributed database system;

wherein the one or more processors on each node configured to:

receive at least one statement being part of a transaction, wherein the transaction is initiated by a client to be executed on a distributed database system;

send a single request to the SEQ-server to create at least one PiT, wherein the SEQ-server provides a logical timestamp counter (LTC) value as a timestamp of the PiT;

upon creation of the at least one PiT, cause execution of the at least one statement, wherein a PiT provides a state and content of committed data in the distributed database system;

upon receiving a commit statement, perform a commitment process of the transaction, wherein the commitment process is based on a commitment timestamp (CMTS) set by the SEQ-server based on an incremented value of the LTC; and

return an acknowledgment of the transaction commitment to the client.

44. The system of claim 43 , wherein the plurality of SEQ-agents are configured at a predefined hierarchy.

45. A non-transitory computer-readable medium storing a set of instructions for managing execution of database transactions by facilitating point-in-time image (PiT), the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a device, cause the device to:

receive at least one statement being part of a transaction, wherein the transaction is initiated by a client to be executed on a distributed database system;

send a single request to a sequencer server (SEQ-server) to create at least one PiT, wherein the SEQ-server provides a logical timestamp counter (LTC) value as a timestamp of the PIT;

upon creation of the at least one PiT, cause execution of the at least one statement, wherein a PiT provides a state and content of committed data in the distributed database system;

upon receiving a commit statement, perform a commitment process of the transaction, wherein the commitment process is based on a commitment timestamp (CMTS) set by the SEQ-server based on an incremented value of the LTC; and

return an acknowledgment of the transaction commitment to the client.

Assignments (1)

Continuity (2)

References Cited (43)