|
If you were logged in you would be able to see more operations.
|
|
|
| Planning Status: |
Unspecified
|
|
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 ;-)
|
|
Description
|
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 ;-) |
Show » |
|
Improvement
Closed
Major
Make mon$statement_id value constant among monitoring snapshots
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. ;)