bug 1195735 only handles TRUNCATE TABLE case - because when the count is updated to zero this is picked up.
But otherwise, this goes into an infinite loop now instead of returning the wrong count...
So as guessed, changes to underlying data not getting reflected.
Maybe we need to re-open the table when a new random scan is started...
bug 1195735 only handles TRUNCATE TABLE case - because when the count is updated to zero this is picked up.
But otherwise, this goes into an infinite loop now instead of returning the wrong count...
So as guessed, changes to underlying data not getting reflected.
Maybe we need to re-open the table when a new random scan is started...