DO or UNDO - there is no VACUUM

VP, Chief Database Scientist @ EnterpriseDB, PostgreSQL Major Contributor and Committer What if PostgreSQL didn’t need VACUUM at all? This seems hard to imagine. After all, PostgreSQL uses multi-version concurrency control (MVCC), and if you create multiple versions of rows, you have to eventually get rid of the row versions somehow. In PostgreSQL, VACUUM is in charge of making sure that happens,

[mumumu-tan]

オッ。VACUUMが消える日が来るか？(*゜ー゜)