The common knowledge is that rollback applies to a statement or transaction as far as I know.
If there is a third type of rollback and this statement indeed was running such a rollback, then 1) that should be documented, 2) it should probably use a separate trx queue state, and when printed out, it should provide some info like "ROLLING BACK bla".
If there isn't a third type of rollback, then 1) how did this statement get into a transient rollback state? 2) how did it get out of it, any potential lose of changes?
The common knowledge is that rollback applies to a statement or transaction as far as I know.
If there is a third type of rollback and this statement indeed was running such a rollback, then 1) that should be documented, 2) it should probably use a separate trx queue state, and when printed out, it should provide some info like "ROLLING BACK bla".
If there isn't a third type of rollback, then 1) how did this statement get into a transient rollback state? 2) how did it get out of it, any potential lose of changes?