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.Dismiss alert
Creating or recreating an index is not logged to MON$STATEMENTS, so you see an active attachment and and active write transaction but you don't know what it is doing.
We have a service checking for long opened write transactions and close the associated attachment after some minutes.
This is for prevent problems in our server when some developers open a query in a developing tool and then go to lunch forgetting to commit it.
But sometime the transaction is valid, for example when it is creating an index on a large table.
Due to this issue we deactivate the service because there is no way to detect what is doing the transaction.
Regards
The text was updated successfully, but these errors were encountered:
It cannot be logged in MON$STATEMENTS, because the index is being rebuilt at commit time, when no statements exist anymore. The same applies to almost all DDL actions. So perhaps MON$TRANSACTIONS should have some indication that it executes some deferred work at the moment.
Submitted by: @kattunga
Creating or recreating an index is not logged to MON$STATEMENTS, so you see an active attachment and and active write transaction but you don't know what it is doing.
We have a service checking for long opened write transactions and close the associated attachment after some minutes.
This is for prevent problems in our server when some developers open a query in a developing tool and then go to lunch forgetting to commit it.
But sometime the transaction is valid, for example when it is creating an index on a large table.
Due to this issue we deactivate the service because there is no way to detect what is doing the transaction.
Regards
The text was updated successfully, but these errors were encountered: