Our index code is flooded with MVCC GC BOUND lines, moreover, our team has already run into problems with GC implicitly working several times, and some patches partially made garbage collection explicit - now some methods are forbidden to call GC, while other methods can do it implicitly, and during MVCC support we have to make sure that these functions are not mixed up. I think it's time to stop and think - about how to make GC engineer-friendly and safe. As far as I'm concerned, the simplest option is an implicit accumulation of rounds, but necessarily an explicit GC call outside the transaction manager code.