You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To minimize the possibility of conflicts, MVCC uses what is called best-effort visibility: for write transactions it chooses read-committed, for read transactions it chooses read-confirmed.
by default task_id:max read confirmed , this is the key reason why duplicates occur in the case of an race condition
Activity
better0fdead commentedon Jun 22, 2023
@R-omk Hi, do you have a reproducer?
R-omk commentedon Jun 22, 2023
I just reported an obvious problem that someone encountered in the telegram chat.
I think you should use
require('txn_proxy')to reproduce issue without external client. (or net box client)driver: fix duplicate id error with mvvc on
driver: fix duplicate id error with mvvc on
driver: fix duplicate id error with mvvc on
driver: fix duplicate id error with mvvc on
driver: fix duplicate id error with mvvc on
driver: fix duplicate id error with mvvc on
driver: fix duplicate id error with mvvc on
driver: fix duplicate id error with mvvc on
drivers: fix concurrency with mvcc
drivers: fix concurrency with mvcc
drivers: fix concurrency with mvcc
driver: fix duplicate id error with mvvc on put
driver: fix duplicate id error with mvvc on on take
driver: fix duplicate id error with mvvc on put and take
driver: fix duplicate id error with mvvc on put and take
driver: fix duplicate id error with mvvc on put and take
driver: fix duplicate id error with mvvc on put and take
driver: fix duplicate id error with mvvc on put and take
driver: fix duplicate id error with mvvc on put and take
drivers: fix concurrency with mvcc
drivers: fix concurrency with mvcc
drivers: fix concurrency with mvcc