Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ALTER INDEX INDEX_NAME ACTIVE is not logged to MON$STATEMENTS [CORE5626] #5892

Open
firebird-automations opened this issue Oct 1, 2017 · 3 comments

Comments

@firebird-automations
Copy link
Collaborator

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

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

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.

@firebird-automations
Copy link
Collaborator Author

Commented by: @kattunga

Yes, something indicating that the transaction is doing some deferred work is enough to distinct it from other open and forgotten transactions.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants