Redis: List Move Notification Fix
Redis merged a fix to make "L move em" keyspace notifications consistent with "L move" regardless of whether source and destination keys match, closing a behavioral inconsistency tracked across two linked issues.
Duration: PT2M19S
Episode overview
This episode is a short developer briefing from Redis.
It explains recent repository work in plain language.
- Show: Redis
- Published: 2026-09-04T13:13:50Z
- Audio duration: PT2M19S
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 4th, and here's what's happening in the Redis codebase.
Today's signal is small in scope but important for correctness: fixing an inconsistency in how list move commands report their own actions.
Pull request 15587, from Gimini-3, addresses "L move em" - that's the multi-key variant of list move. Until now, the order of keyspace notifications it emitted depended on whether you were moving elements within the same key or between two different keys. When source and destination were different keys, Redis…
This PR aligns both paths, so same-key moves now emit push before pop, just like distinct-key moves. The change also extends to "BL move em," the blocking version, since it shares the same underlying move logic once execution starts. The team backed this with regression tests covering same-key moves, distinct-key…
The fix was tracked across two linked issues, numbers 3855 and 15586, and companion documentation updates landed in the Redis docs repository to formally describe the correct push-before-pop ordering for "L move" and "BL move" going forward.
Why this matters: keyspace notifications are how downstream consumers - replication listeners, cache…
Nearby episodes from Redis
- Module Update and a Timing-Sensitive Test Fix
- Stability Under Pressure
- Faster RDB Loads, Steadier Tests
- Cleaning Up Data Integrity Gaps
- Weekly Recap - Closing Correctness Gaps in Clustering and Access Control
- Cleaning Up Hash Field Expiration
- Cluster Bus Security and a Flaky Test Fix
- Quietly Failing Configs Get a Voice