Skip to content

Commit f8987bc

Browse files
joshkang97meta-codesync[bot]
authored andcommitted
Include PR and version for range tombstone blog post (#14875)
Summary: Pull Request resolved: #14875 title Reviewed By: pdillinger Differential Revision: D109353179 fbshipit-source-id: c14c9ecbd29a8118b1d0f0689e2f29c162bd15e8
1 parent 30f42e0 commit f8987bc

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎docs/_posts/2026-06-22-range-tombstone-conversion.markdown‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Because the tombstone lives in the memtable, it follows the normal lifecycle fro
6565

6666
## Enabling it
6767

68-
Range tombstone conversion is controlled by the column-family option `min_tombstones_for_range_conversion`: the minimum length of a contiguous point-tombstone run that triggers a conversion. The default is `0`, which disables the feature. Set it to a positive value to turn it on; the option is dynamically changeable through `SetOptions`, so you can enable or tune it without reopening the database.
68+
Range tombstone conversion landed in [PR #14448](https://github.com/facebook/rocksdb/pull/14448) (plus a few additional follow-up bug fixes) and is available in RocksDB 11.3.0 and later. It is controlled by the column-family option `min_tombstones_for_range_conversion`: the minimum length of a contiguous point-tombstone run that triggers a conversion. The default is `0`, which disables the feature. Set it to a positive value to turn it on; the option is dynamically changeable through `SetOptions`, so you can enable or tune it without reopening the database.
6969

7070
```cpp
7171
Options options;

0 commit comments

Comments
 (0)