Redis: Stream Trim Persistence Risk and Cleaner Scans
Three focused reliability fixes landed with no single sweeping pattern. The highest-impact item is PR #15825, where stream trim by minimum ID can leave empty nodes that fail later saves, alongside cleaner CLI scans in PR #15817 and a test race fix in PR #15805.
Duration: PT2M14S
Episode overview
This episode is a short developer briefing from Redis.
It explains recent repository work in plain language.
- Show: Redis
- Published: 2026-09-20T13:12:46Z
- Audio duration: PT2M14S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's September 20th, 2026, and this is your Redis developer briefing.
The takeaway today is straight forward: no single sweeping change, but three small reliability fixes, with one persistence risk that deserves your attention first.
Starting with streams. Pull request 15825 addresses a case where trimming a stream by minimum ID can leave a storage node in the index with zero live entries. That happens after a deleted entry tombstones the end of a node, so the trim logic no longer qualifies the whole node for removal, but still marks the…
Second, observability without side effects. Merged pull request 15817, also seen as commit c 00 f 920, enables client no-touch mode for the redis command line tools big keys, memory keys, and key stats modes. Previously, those size scans performed normal reads, which on least-recently-used or least-frequently-used…
Finally, test stability. Merged pull request 15805, also seen as commit 5 f 08991, fixes a race in the A O F duration test module where a background worker released held command arguments after unlocking and unblocking the client, racing with slow log recording on the main thread. The solution keeps the release…
What's next:…
Nearby episodes from Redis
- Scan Command Cleanup
- Security Patches Ship Across Five Release Lines
- Data Correctness Fixes Across Streams, Sorted Sets, and Scripting
- Security Patches Roll Backward Across Four Release Lines
- Trust Boundaries Get Tighter
- Checksum Performance and a Version Bump Cluster
- Weekly Recap - Correctness Fixes and Read-Path Performance
- Hardening Under Concurrency