Currently, removal of schema objects such as tables, indexes, and tenants are done by changing the descriptor visibility and scheduling a job to remove the object data using ClearRange once the GC TTL expires. However, as described in #69380, when DeleteRange is changed to use MVCC range tombstones in #70415 we should use DeleteRange to remove these objects instead. This includes removing the schema GC jobs entirely, and relying on MVCC GC to remove the data when the TTL expires (requires #70414).
There is a much cheaper initial option in #76105.
Related to #31563.
Epic CRDB-2624
Jira issue: CRDB-10070
Currently, removal of schema objects such as tables, indexes, and tenants are done by changing the descriptor visibility and scheduling a job to remove the object data using
ClearRangeonce the GC TTL expires. However, as described in #69380, whenDeleteRangeis changed to use MVCC range tombstones in #70415 we should useDeleteRangeto remove these objects instead. This includes removing the schema GC jobs entirely, and relying on MVCC GC to remove the data when the TTL expires (requires #70414).There is a much cheaper initial option in #76105.
Related to #31563.
Epic CRDB-2624
Jira issue: CRDB-10070