aboutsummaryrefslogtreecommitdiff
path: root/src/leveldb/TODO
diff options
context:
space:
mode:
Diffstat (limited to 'src/leveldb/TODO')
-rw-r--r--src/leveldb/TODO14
1 files changed, 0 insertions, 14 deletions
diff --git a/src/leveldb/TODO b/src/leveldb/TODO
deleted file mode 100644
index e603c07137..0000000000
--- a/src/leveldb/TODO
+++ /dev/null
@@ -1,14 +0,0 @@
-ss
-- Stats
-
-db
-- Maybe implement DB::BulkDeleteForRange(start_key, end_key)
- that would blow away files whose ranges are entirely contained
- within [start_key..end_key]? For Chrome, deletion of obsolete
- object stores, etc. can be done in the background anyway, so
- probably not that important.
-- There have been requests for MultiGet.
-
-After a range is completely deleted, what gets rid of the
-corresponding files if we do no future changes to that range. Make
-the conditions for triggering compactions fire in more situations?