Issue Details (XML | Word | Printable)

Key: CORE-5739
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Pavel Zotov
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Firebird Core

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

Created: 02/Feb/18 05:47 PM   Updated: 02/Feb/18 06:49 PM
Component/s: Engine
Affects Version/s: None
Fix Version/s: None

QA Status: No test


 Description  « Hide
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.


 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Dmitry Yemanov added a comment - 02/Feb/18 06:13 PM
I suggest to report "signalled-to-be-deleted" attachments via MON$STATE = -1.

Pavel Zotov added a comment - 02/Feb/18 06:35 PM
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.

Dmitry Yemanov added a comment - 02/Feb/18 06:49 PM
We cannot add new fields in point releases, so the solution should be in sync between existing and future versions.