vinyl: remove mutex around transaction conflict manager
The only case when the tx manager was used from the backend was to query the oldest active read view. Instead of querying from the backend, maintain a sequence and update it whenever the oldest read view is advanced.
Loading
Please register or sign in to comment