Storage server now uses max_frame_no from the txn to read frames
It will make sure to not read any frames beyond the max_frame_no
of the transaction. This fixes the bug in the isolation level.
Storage server now checks max_frame_no before inserting. If it
has changed meanwhile, then it rejects the insertion request.
This lets us have multiple (non concurrent) writers or even multiple
logical primary instances.
max_frame_no
from the txn to read frames It will make sure to not read any frames beyond themax_frame_no
of the transaction. This fixes the bug in the isolation level.max_frame_no
before inserting. If it has changed meanwhile, then it rejects the insertion request.This lets us have multiple (non concurrent) writers or even multiple logical primary instances.
Minor changes: