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

Make mon$statement_id value constant among monitoring snapshots [CORE2305] #2729

Closed
firebird-automations opened this issue Feb 4, 2009 · 12 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @WarmBooter

Votes: 1

The value of mon$statement_id may change for the same running statement in different "monitoring snapshots". This makes difficult, for example, for monitoring applications to identify the same query, since it keeps "refreshing" the data by closing and opening the monitoring transaction and so, may get different numbers for the mon$statement_id,

BTW, Dmitry Yemanov told me that the currently behavior may change in 2.5. I'm adding this to the tracker so he will not forget about it ;-)

Commits: 86ea2dd 1974ff6

====== Test Details ======

See comment in .fbt:

    /\*
    \-\- todo later, after fix [CORE4796](https://github.com/FirebirdSQL/firebird/issues?q=CORE4796+in%3Atitle)
    'merge into tdetl t '
    \|\| 'using \( select 5 as id, 1 as pid from rdb$types rows 2 \) s '
    \|\| 'on <http://t.id=s.id> '
    \|\| 'when matched then update set t\.pid = s\.pid '
    \|\| 'when not matched then insert values\( <http://s.id>, s\.pid\)';
    \*/
@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @WarmBooter

summary: Make mon$statement_id value constant among => Make mon$statement_id value constant among monitoring snapshots

@firebird-automations
Copy link
Collaborator Author

Commented by: Douglas Tosi (douglasht)

+1!
If I could vote 1.000 times for this issue, I would.
The current behavior is really counter intuitive (not to mention it's a royal PITA). I should know, I work with monitoring tables all day long. ;)

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Fix Version: 3.0 Alpha 1 [ 10331 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => In Progress [ 3 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Fix Version: 2.5.1 [ 10333 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Version: 2.5.0 [ 10221 ]

Version: 3.0 Initial [ 10301 ]

Version: 2.1.3 [ 10302 ]

Version: 2.1.0 [ 10041 ]

Component: Engine [ 10000 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: In Progress [ 3 ] => Open [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: Done successfully

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: Done successfully => Done with caveats

Test Details: See comment in .fbt:

    /\*
    \-\- todo later, after fix [CORE4796](https://github.com/FirebirdSQL/firebird/issues?q=CORE4796+in%3Atitle)
    'merge into tdetl t '
    \|\| 'using \( select 5 as id, 1 as pid from rdb$types rows 2 \) s '
    \|\| 'on <http://t.id=s.id> '
    \|\| 'when matched then update set t\.pid = s\.pid '
    \|\| 'when not matched then insert values\( <http://s.id>, s\.pid\)';
    \*/

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