...
Each read operation outside active transaction creates a special read only transaction and uses its tx snapshot for versions filtering.Each read operation within active READ_COMMITTED transaction creates a special read only transaction and uses its tx snapshot for versions filtering
RO transactions are added to active Tx lists on reader (near) node and MVCC coordinator.
On reaer node failure all RO txs are removed from the active Tx list on MVCC coordinator.
Each read operation within active REPEATABLE_READ transaction uses its tx snapshot for versions filtering (REPEATABLE_READ semantics).
During get operation the first passing MVCC filter item is returned.
During secondary indexes scans 'ver' field of tree item is checked, if row version is visible (the row was added by current or committed tx) 'xid_max' field of referenced data row is checked - the row considered as visible if it is the last version of row 'xid_max' is NA or ACTIVE or ABORTED or higher than assigned.
During primary indexes scans 'ver' field of tree item is checked, if row version is visible (the row was added by current or committed tx) 'xid_max' field of referenced data row is checked - the row considered as visible if it is the last version of row 'xid_max' is NA or ACTIVE or ABORTED or higher than assigned.
...
Delete consists of next steps:
...