Home
last modified time | relevance | path

Searched refs:covered (Results 1 – 6 of 6) sorted by relevance

/rocksdb-6.9/db_stress_tool/
Ddb_stress_shared_state.h282 int covered = 0; in DeleteRange() local
285 ++covered; in DeleteRange()
288 return covered; in DeleteRange()
Dno_batched_ops_stress.cc500 int covered = shared->DeleteRange(rand_column_family, rand_key, in TestDeleteRange() local
504 thread->stats.AddCoveredByRangeDeletions(covered); in TestDeleteRange()
/rocksdb-6.9/docs/_posts/
D2017-09-28-rocksdb-5-8-released.markdown24 * Fix transient reappearance of keys covered by range deletions when memtable prefix bloom filter i…
D2018-11-21-delete-range.markdown157 …skyline is expensive to construct but fast to determine whether a key is covered. The skyline keep…
219 covered (though we do still check the current level since there may be keys written after
/rocksdb-6.9/
DCOPYING17 using it. (Some other Free Software Foundation software is covered by
73 covered by this License; they are outside its scope. The act of
75 is covered only if its contents constitute a work based on the
DHISTORY.md12 … tombstones were read from those incorrectly cached blocks, the keys they covered would be exposed.
256 * Fix flush's/compaction's merge processing logic which allowed `Put`s covered by range tombstones …
377 * Fixed Get correctness bug in the presence of range tombstones where merge operands covered by a r…
596 * Fix transient reappearance of keys covered by range deletions when memtable prefix bloom filter i…