storage: ensure readAsOfIterator caches rangekeys #84714
Labels
A-disaster-recovery
A-kv-replication
Relating to Raft, consensus, and coordination.
branch-release-22.2
Used to mark GA and release blockers, technical advisories, and bugs for 22.2
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
T-disaster-recovery
Currently, the readAsOfIterator calls the expensive
f.iter.RangeKeys()
every timef.iter.HasPointAndRange == (true,true)
. Consequently, if RESTORE encounters a range key, it faces a steep performance hit.Instead, if the range bounds during iteration remain the same, the range keys should be cached. This should be solved by #84379, but if that doesn't land by 22.2, then the readAsOfIterator will need to manually cache range keys.
Jira issue: CRDB-17824
Epic CRDB-2624
The text was updated successfully, but these errors were encountered: