Unverified50% confidenceFactExact time
Multi-version concurrency control (MVCC) generates new versions of data while retaining old versions, allowing read operations to choose a consistent snapshot based on the transaction start time without waiting for write operations to complete.
1
Sources
50%
Confidence
Long-term
Relevance
10/14/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWAL 通过重放日志实现崩溃恢复，MVCC 通过为每条记录维护多个版本（xmin/xmax 标记）实现读写不阻塞，由 VACUUM 进程清理过期版本68% similarUnverifiedInnoDB's MVCC is implemented by modifying rows in place and tracking old versions with an undo chain: each row hides a transaction ID and a rollback pointer, and the rollback pointer strings together old versions in the undo log to form a version chain; read committed (RC) generates a new snapshot on each statement execution, while repeatable read (RR) generates a snapshot at transaction start.64% similarUnverifiedCursor needs to periodically merge upstream VSCode updates, and version synchronization typically has a delay of days to weeks, which may cause compatibility issues for some extensions that depend on the latest APIs.63% similarUnverifiedIn primary-replica replication, asynchronous replication mode does not require the primary to wait for replica acknowledgment before committing transactions, resulting in replication lag; semi-synchronous mode requires at least one replica to acknowledge before returning success, reducing the risk of data loss but increasing write latency.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1030897API
curl https://kongchang.com/api/v1/knowledge/claims/1030897MCP
get_claim(id=1030897)