[2pt] feedback: Transactions | Expand on transaction problem types

Product: Tarantool
Audience/target: dev
Root document: https://www.tarantool.io/en/doc/latest/book/box/atomic/
SME: @ alyapunov

Details

Problem types:
dirty read
non-repeatable read
phantom read
dirty write
cursor lost update
lost update
read skew
write skew
(Write skew is not the only possible problem)

We might expand on the transaction problem types resolved by the conflict manager, simply listing the above types.

<…>oment of the beginning of the transaction
(that is not common).
|The conflict manager makes decisions on whether and when each transaction gets
which snapshot. That allows to avoid some conflicts comparing with classical
snapshot isolation approach|.

https://www.tarantool.io/en/doc/latest/book/box/atomic/

This is vague, could you please explain this further: what decisions and what problems? Are you referring to the problem of write skews typical of SI level? Thanks

Start with the linked root document, especially the transaction and conflict-manager explanation. Compare it with the requested list of transaction problem types and clarify which problems the conflict manager resolves and what decisions it makes; done means the section answers those questions without the current vague wording.