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

Jump to bottom

Add ability to see in mon$attachments: 1) whether some attach was notified that he must be deleted; 2) timestamp of such notification [CORE5739] #6003

Open
firebird-automations opened this issue Feb 2, 2018 · 3 comments
Open

Add ability to see in mon$attachments: 1) whether some attach was notified that he must be deleted; 2) timestamp of such notification [CORE5739] #6003

firebird-automations opened this issue Feb 2, 2018 · 3 comments
Labels
component: engine priority: minor type: improvement

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @pavel-zotov

In weird (rare) cases one may to explore that mon$attachments has record(s) related to some non-killed attachments, despite that we issue 'delete from mon$attachments' many times.
This attachment does not link to any running client (isql or anotherapp.), but is *does* occupy DB handle and prevent it from change to shutdown state.
It will be useful to add in mon$attachments table two fields with detalization about this "strange" record:
1) flag that this attach was notified that he must gone, and
2) timestamp of such notification.

PS.
Ticket has been created after discuss with dimitr.
@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

I suggest to report "signalled-to-be-deleted" attachments via MON$STATE = -1.

@firebird-automations
Copy link
Collaborator Author

Commented by: @pavel-zotov

BTW: may be only one field is required, like "mon$delete_signal_timestamp" ?
If it is null than attachment was not notified, otherwise - signal was sent to him at corresponding time.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

We cannot add new fields in point releases, so the solution should be in sync between existing and future versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: engine priority: minor type: improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@firebird-automations