On 1/1/21 8:14 AM, tsunakawa.ta...@fujitsu.com wrote:
--------------------------------------------------
11. A method comprising:
receiving information relating to a distributed database transaction operating
on data in data stores associated with respective participating nodes
associated with the distributed database transaction;
requesting commit time votes from the respective participating nodes, the
commit time votes reflecting local clock values of the respective participating
nodes;
receiving the commit time votes from the respective participating nodes in
response to the requesting;
computing a global commit timestamp for the distributed database transaction
based at least in part on the commit time votes, the global commit timestamp
reflecting a maximum value of the commit time votes received from the
respective participating nodes; and
synchronizing commitment of the distributed database transaction at the
respective participating nodes to the global commit timestamp,
wherein at least the computing is performed by a computing device.
Thank you for this analysis of the patent.
After researching in depth, I think this is the real problem.
My idea was that we are not using real clocks, we only use clock ticks
to measure time intervals. It can also be interpreted as a kind of clock.
That we can do:
1. Use global clocks at the start of transaction.
2. Use CSN-based snapshot as a machinery and create an extension to
allow user defined commit protocols.
--
regards,
Andrey Lepikhov
Postgres Professional