1.3.2
Overview
This release fixes a problem with duplicate id error with mvvc on put and take.
Bugfixes
- Duplicate id error with mvvc on put and take (#207).
Let's consider the problem on the example of executing twoput
commands one by one.
MVCC uses so-called best-effort visibility to minimize the probability of conflicts: read-committed is selected for write transactions and read-confirmed for read transactions. Which leads to a situation where a task gets a new id and yields while waiting to write to WAL and at the same time the second task gets the same id (because the record with the new id has not yet received confirmed status) and fails when trying to write.