Hi postgresql hackers -
I would like to find some analysis (published work, blog posts) on the overheads affiliated with the guarantees
providedby MVCC isolation. More specifically, assuming the current workload is CPU bound (as opposed to IO) what is the
CPUoverhead of generating the WAL, the overhead of version checking and version creation, and of garbage collecting old
andunnecessary versions? For what it’s worth, I am working on a research project where it is envisioned that some of
thiswork can be offloaded.
Thank you,
Pete Stevenson
