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
Comments
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @WarmBootersummary: Make mon$statement_id value constant among => Make mon$statement_id value constant among monitoring snapshots |
Commented by: Douglas Tosi (douglasht) +1! |
Modified by: @dyemanovFix Version: 3.0 Alpha 1 [ 10331 ] |
Modified by: @dyemanovstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @dyemanovFix Version: 2.5.1 [ 10333 ] |
Modified by: @dyemanovVersion: 2.5.0 [ 10221 ] Version: 3.0 Initial [ 10301 ] Version: 2.1.3 [ 10302 ] Version: 2.1.0 [ 10041 ] Component: Engine [ 10000 ] |
Modified by: @dyemanovstatus: In Progress [ 3 ] => Open [ 1 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: Done successfully => Done with caveats Test Details: See comment in .fbt:
|
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:
The text was updated successfully, but these errors were encountered: