Unverified50% confidenceFactExact time
Old versions of tuples under MVCC are reclaimed by the VACUUM process before they are no longer referenced by any active transaction snapshot, and long transactions prevent old versions from being reclaimed, causing disk bloat.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWAL 通过重放日志实现崩溃恢复，MVCC 通过为每条记录维护多个版本（xmin/xmax 标记）实现读写不阻塞，由 VACUUM 进程清理过期版本71% 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.66% similarUnverifiedrc.8新版本的数据结构与旧版不兼容，升级前需要做好数据备份与迁移63% similarUnverifiedWindows 原生剪贴板只能保存最近一次复制的内容，新内容一来旧内容立刻消失60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1040287API
curl https://kongchang.com/api/v1/knowledge/claims/1040287MCP
get_claim(id=1040287)