Bug #58463
RocksDBTransactionImpl::rm_range_keys doesn't use bound iterator
Status:
Pending Backport
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
backport_processed
Backport:
quincy, pacific, reef
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Hence this might cause slow omap enumeration when rocksdb has got tons of tombstones.
Related issues
History
#1 Updated by Igor Fedotov 2 months ago
- Status changed from New to Fix Under Review
- Pull request ID set to 49748
#2 Updated by Yuri Weinstein about 12 hours ago
#3 Updated by Igor Fedotov about 3 hours ago
- Backport changed from quincy, pacific to quincy, pacific, reef
#4 Updated by Igor Fedotov about 3 hours ago
- Status changed from Fix Under Review to Pending Backport
#5 Updated by Backport Bot about 3 hours ago
- Copied to Backport #59138: pacific: RocksDBTransactionImpl::rm_range_keys doesn't use bound iterator added
#6 Updated by Backport Bot about 3 hours ago
- Copied to Backport #59139: reef: RocksDBTransactionImpl::rm_range_keys doesn't use bound iterator added
#7 Updated by Backport Bot about 3 hours ago
- Copied to Backport #59140: quincy: RocksDBTransactionImpl::rm_range_keys doesn't use bound iterator added
#8 Updated by Backport Bot about 3 hours ago
- Tags set to backport_processed