You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the field rdb$index_segments.rdb$statistics for any GTT contains the value that is result of LATEST issued set statistics command.
If this command was issued from ANOTHER connect we can see wrong values for OUR records of GTT.
The worst thing is that execution plan in OUR connect could not be explained since some moment when old ("good") values were overwritten by someone.
So it is better to show such values as result of quering of index root page rather than rdb$-table.
The text was updated successfully, but these errors were encountered:
I'm not sure I like the idea. System tables are persistent and their access rules are straightforward. Offering some kind of "virtual" fields that would show different values for different connections/transactions does not fit the concept of the RDB$ tables, IMHO. I'd rather think about some other solution.
Submitted by: @pavel-zotov
Currently the field rdb$index_segments.rdb$statistics for any GTT contains the value that is result of LATEST issued set statistics command.
If this command was issued from ANOTHER connect we can see wrong values for OUR records of GTT.
The worst thing is that execution plan in OUR connect could not be explained since some moment when old ("good") values were overwritten by someone.
So it is better to show such values as result of quering of index root page rather than rdb$-table.
The text was updated successfully, but these errors were encountered: