I committed bottom-up index deletion today, which is slated for Postgres 14. See postgresql.org/docs/devel/btr for a detailed description. In short: it makes index bloat/VACUUM issues much less likely to get out of hand. Updaters are now *required* to clean up indexes after themselves.
Conversation
Replying to
You're welcome, Stefanie! I was very glad to have something to distract me from everything over the past year.
7
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Replying to
Thanks! Not sure about that. These tableams shouldn't need this mechanism by definition IMV. A clustered index (or whatever) has 100% stable logical identifiers (e.g., PK values, not Postgres heap TIDs). No "version chaining" in indexes for updates can be possible to begin with.
2
4
Show replies
Replying to
Thanks!
I love the documentation, which I think makes me understand the feature: Heavily updated tuples which do not have their (indexed) values changed will trigger bottom-up deletion if an index predicts a split.
Huge for some workloads!
2
