summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Kryczka <andrewkr@fb.com>2020-10-12 12:44:33 -0700
committerAndrew Kryczka <andrewkr@fb.com>2020-10-12 13:15:15 -0700
commit878b3a41de96aefd67e9d94860b60a1bedf6320f (patch)
treef938ab4d7d321ad1ed8fdaac05ff922d684936c3
parentf36f44c5e6e36595c71fc5c2a29f4a1bad6d474d (diff)
update HISTORY.md and version.h for 6.11.6v6.11.6
-rw-r--r--HISTORY.md2
-rw-r--r--include/rocksdb/version.h2
2 files changed, 2 insertions, 2 deletions
diff --git a/HISTORY.md b/HISTORY.md
index 535d79542..b2bcbe6e0 100644
--- a/HISTORY.md
+++ b/HISTORY.md
@@ -1,5 +1,5 @@
# Rocksdb Change Log
-## Unreleased
+## 6.11.6 (10/12/2020)
### Bug Fixes
* Fixed a bug in the following combination of features: indexes with user keys (`format_version >= 3`), indexes are partitioned (`index_type == kTwoLevelIndexSearch`), and some index partitions are pinned in memory (`BlockBasedTableOptions::pin_l0_filter_and_index_blocks_in_cache`). The bug could cause keys to be truncated when read from the index leading to wrong read results or other unexpected behavior.
* Fixed a bug when indexes are partitioned (`index_type == kTwoLevelIndexSearch`), some index partitions are pinned in memory (`BlockBasedTableOptions::pin_l0_filter_and_index_blocks_in_cache`), and partitions reads could be mixed between block cache and directly from the file (e.g., with `enable_index_compression == 1` and `mmap_read == 1`, partitions that were stored uncompressed due to poor compression ratio would be read directly from the file via mmap, while partitions that were stored compressed would be read from block cache). The bug could cause index partitions to be mistakenly considered empty during reads leading to wrong read results.
diff --git a/include/rocksdb/version.h b/include/rocksdb/version.h
index bf974d5b9..033a8cab5 100644
--- a/include/rocksdb/version.h
+++ b/include/rocksdb/version.h
@@ -6,7 +6,7 @@
#define ROCKSDB_MAJOR 6
#define ROCKSDB_MINOR 11
-#define ROCKSDB_PATCH 5
+#define ROCKSDB_PATCH 6
// Do not use these. We made the mistake of declaring macros starting with
// double underscore. Now we have to live with our choice. We'll deprecate these