Redis: Set Expiry Accounting Fix and Hashing Cleanup
Two unrelated changes landed: a correctness fix for allocation accounting when lazy expiry deletes sets in PR 16196, and a SHA-256 message schedule simplification in PR 16194. No broader pattern emerged; the set accounting fix carries the highest reliability impact.
Duration: PT2M15S
Episode overview
This episode is a short developer briefing from Redis.
It explains recent repository work in plain language.
- Show: Redis
- Published: 2026-11-07T14:09:28Z
- Audio duration: PT2M15S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Hello, this is your Redis briefing for November 7th, 2026.
Today's activity doesn't point to a single trend — it's two narrow, unrelated changes, and the highest-impact one is a correctness fix for expiring set members.
First, reliability in memory tracking. Pull request 16196 addresses lazy expiry during set membership checks. When commands probe for a member that has logically expired, Redis removes it in the background. If that was the last member, the key itself is deleted, but on that path the per-key allocation size update…
Second, small performance and readability work in hashing. Pull request 16194 simplifies how the first part of the S H A 256 message schedule is loaded, replacing manual byte shifting and combining with a single explicit big-endian 32-bit load helper. Functionally it's the same hash, but the code is clearer about…
What's next: watch for test results on debug builds covering expired sets, and any follow-up measurements confirming the hashing cleanup performs as intended. No broader refactor is signaled — treat both as isolated maintenance.
That's it for today — thanks for listening.
Nearby episodes from Redis
- Replica Divergence Fixes and Sampling Speedups
- Slot Migration Safety and Scripting Guardrails
- Weekly Recap - Data Safety, Sorted Sets, and Observability
- Bloom Filters Eyed for Core, Replication Fixes Land
- Integrity Fixes and Sorted-Set Tuning
- Durability Fixes and Slow Log Clarity
- Listpack Compatibility Fix and Sorted Set Hardening
- Storage Safety Fixes and Native Bloom Proposal