How Postgres Makes Transactions Atomic

Re:How Postgres Makes Transactions Atomic by petergeoghegan on Thursday August 17, 2017 @02:25AM (#15034221)

I guess that I said HOT UPDATE because you talked about HOT. What you describe goes against how visibility information is maintained. There is an interlock between indexes and tables for VACUUM that would have to be considered. It would be hard to set an all-visible bit on a leaf page in a race-free manner.

A much simpler way of putting it would be that deletes would have to touch indexes if summarized visibility info was stored in indexes, even in cases where overall there is hardly any benefit from putting per-page visibility information in index pages. It's not impossible to make something like this work, but it's not obviously compatible with the current design.

I'm glad that you found UPSERT useful.

[ Parent | on HN ]

Re:How Postgres Makes Transactions Atomic by felixge on Thursday August 17, 2017 @03:51AM (#15034608)

I wasn't really proposing to change how visibility information is maintained, my grasp on the internals is far to weak for that :). I just tried to make sure I understood your comment, which I think I do now. So thanks again for another insightful reply :)

[ Parent | on HN ]