-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Compaction
-
None
-
Storage Engines, Storage Engines - Persistence
-
SE Persistence - 2025-09-26
-
2
I am suspicious of this section in compaction:
/* All the keys with the specified prefix have been parsed. */ if (ret == WT_NOTFOUND) { full_iteration = true; continue; }
I wonder if we should reset ret to 0 here, because we proceed with continue with a WT_NOTFOUND assigned to ret and that seems to be wrong.
- is related to
-
WT-15485 Add configuration to control app thread eviction when minimum cache fill ratio is reached
-
- Closed
-
-
WT-15544 Fix internal_uri memory leak in __wt_cursor_init
-
- Closed
-
-
WT-15547 Simplify paths when printing the error log
-
- Closed
-
-
WT-15559 Update tools/callgraph to the most recent version
-
- Closed
-
- related to
-
WT-15461 Merge WT-14542 into develop branch
-
- Closed
-
-
WT-15485 Add configuration to control app thread eviction when minimum cache fill ratio is reached
-
- Closed
-
-
WT-15557 Use check and reset macro to refactor existing code.
-
- Open
-
-
WT-15421 Increase PALM's cache_size_mb in python tests
-
- Closed
-
-
WT-14542 Enable caching for layered cursors and their constituents in WT
-
- Closed
-
-
WT-14246 stat.dsrc.btree_entries off by one in test_stat04
-
- Closed
-
-
WT-15638 3.59% decrease in Update count in Variant amazon2023-perf-tests-arm64 for Task perf-test-log-small-files in Test log.wtperf
-
- Closed
-