rodrigogoncalves wrote:
What I don't understand is why there is a performance issue when an CommitRetaining is applied. Since the comands related to the transaction won't be "rollbacked" anymore, other transaction have no interest on this one anymore, so they should not have a performance impact.
Ann W.Harrison answers:
The problem is that a commit retaining starts a new transaction that keeps the same context as the one that was "commit retained". From the point of view of garbage collection, it's as if that transaction were still running, and it block garbage collection at the state when the original transaction started.
We've been kicking around a change that would reduce the impact of read-committed transactions, but it's in a tricky part of the code and I don't know when it will show up.