Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

Postgres uses MVCC, which is basically copy-on-write: every UPDATE to a row actually creates a new row. Once all transactions that could see the old row have finished, the old row can be pruned.


Ah, thanks for the clarification - the bloat issue makes more sense now.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: