Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- storex-perf

Assigned Teams:

Storage Execution
Backwards Compatibility:
Fully Compatible
Sprint:
Execution Team 2023-12-25, Execution Team 2024-01-08, Execution Team 2024-01-22
Linked BF Score:
20
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

The new WT_CURSOR bound feature is more efficient than a search_near if we set a lower bound and call next() or set an upper bound and call prev().

The important cases we know about are already tracked in other tickets, but there is at least one case in seekNear that could take advantage of a bounded cursor.

depends on

WT-11911 Fix use-after-free with bounded cursor and search_near

Closed

WT-11957 Calling next() is not idempotent with bounded cursors and prepare conflicts

Closed

is related to

SERVER-84748 Index cursors no longer need callers to provide KeyStrings with discriminators

Backlog

SERVER-65527 Use range bounded cursors in place of prefix search_near on unique indexes

Closed

SERVER-69093 Use range bounded cursors for restoring cursors in the record store after yielding

Closed

related to

SERVER-78365 Investigate removing ignore_prepare=force

Backlog

(1 related to)

Assignee:: Louis Williams
Reporter:: Louis Williams
Participants:: Githook User, Jie Chen, Louis Williams
Votes:: 0 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: Jul 28 2022 08:32:38 AM UTC
Updated:: Mar 22 2024 07:34:39 PM UTC
Resolved:: Jan 16 2024 06:24:09 PM UTC
Confidence Status Last Update:: 19/Dec/23 9:26 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates