This isn’t wrong at all, but… 1. A lot of it is heavily dependent on implementation details. (Yeah we have to care about XID, but we shouldn’t have to care abo

This isn’t wrong at all, but… 1. A lot of it is heavily dependent on implementation details. (Yeah we have to care about XID, but we shouldn’t have to care about it exponentially for nested scope workloads once that scope exits.) 2. Actual nested transactions could help alleviate that without too much burden on the MVCC implementation. (This would provide a mechanism for isolating and cleaning up scoped XIDs.)