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
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
My answer is legalistic, though. The fact that I don't really know how such a tableam (e.g. Zedstore) fits in here seems like a real problem. But that would be true with or without my patch. I'm willing to have this more general discussion if there are any takers!