summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--src/third_party/wiredtiger/import.data2
-rw-r--r--src/third_party/wiredtiger/src/docs/cursor-ops.dox8
2 files changed, 9 insertions, 1 deletions
diff --git a/src/third_party/wiredtiger/import.data b/src/third_party/wiredtiger/import.data
index 0381b75fc61..f95bcd13adf 100644
--- a/src/third_party/wiredtiger/import.data
+++ b/src/third_party/wiredtiger/import.data
@@ -2,5 +2,5 @@
"vendor": "wiredtiger",
"github": "wiredtiger/wiredtiger.git",
"branch": "mongodb-master",
- "commit": "dfc1385ec8b2aa0d86dfe66890a7e3b95b729d43"
+ "commit": "6873ef7d0c3f3babc28cdc4a16cc302038e51334"
}
diff --git a/src/third_party/wiredtiger/src/docs/cursor-ops.dox b/src/third_party/wiredtiger/src/docs/cursor-ops.dox
index 9618396a77c..c6d0d30b827 100644
--- a/src/third_party/wiredtiger/src/docs/cursor-ops.dox
+++ b/src/third_party/wiredtiger/src/docs/cursor-ops.dox
@@ -70,6 +70,14 @@ WT_CURSOR::search_near method:
@snippet ex_cursor.c cursor search near
+The WT_CURSOR::search_near method can also be used with a prefix key by
+setting \c prefix_search=true in the cursor configuration options. This
+optimization ensures that search_near only traverses the relevant key
+range with the matching prefix. Limiting the key range that search_near
+can traverse through is particularly useful when there are a larger number
+of records present outside of the key range which are not visible to the
+search_near caller.
+
Cursor positions do not survive transactions: cursors that are open during
WT_SESSION::begin_transaction, WT_SESSION::commit_transaction or
WT_SESSION::rollback_transaction will lose their position as if