*: avoid non-MVCC operations #70429
Description
As described in #69380, we want to replace use of non-MVCC commands such as ClearRange, RevertRange, and AddSSTable with MVCC-compliant alternatives, as these violate invariants that other components rely on. This involves:
MVCC range deletion tombstones
- db: support range-key => value pebble#1339
- storage: MVCC range deletion tombstones #70412
- kvserver: garbage collect MVCC range tombstones #70414
- kvserver: use MVCC range tombstones in
DeleteRange#70415 - kvserver: MVCC-compliant
RevertRangevariant #70416 - kvserver: support MVCC range tombstones in
Export#71398 - batcheval: support MVCC range tombstones in
AddSSTable#76234 - backup: MVCC Bulk Operations Are Missing from Backups #71155
- sql: migrate schema object removals and GC to
DeleteRange#70427 - sql: migrate bulk job cancellation to
DeleteRange#70428 - kvserver: emit MVCC range tombstones across rangefeeds #82449
- kvserver: C2C handling of
DeleteRangeaka MVCC range tombstones #70433
AddSSTable at current timestamp
- kvserver:
AddSSTableoption to write at current timestamp #70422 - storage: optimize
UpdateSSTTimestamps()#72528 - sql: incremental index backfills #70426
- kvserver: rangefeed handling of
AddSSTable#70434 - rangefeed: memory accounting and budgeting #73616
Epic CRDB-2624
Jira issue: CRDB-10072