You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
After commit\rollback retaining transaction has a new number (but only when there are any changes to the database). This significantly complicates analysis of trace reports, as it's not easy to link events to the transaction context as transaction may change identity.
It would be nice if trace entry for COMMIT/ROLLBACK RETAINING events would include both: original (or previous) transaction ID and new transaction ID, so trace log parsers could properly link events to transactions and retaining transactions into a chain.
here "(TRA_1060844, CONCURRENCY | WAIT | READ_WRITE)" is old transaction identifier, as it reported in events before COMMIT_RETAINING, and
"New number 1060845" is a new line with new transaction ID assigned by COMMIT_RETAINING.
Note, new number could be the same as old number - if transaction modifies no rows.
After such "commit\rollback retaining" event transaction identifier will be reported appended with its initial number: