Skip to content
HotKVDocs

Ask the HotKV docs

Answers come only from these docs and can be wrong; check the linked pages before you rely on them.

ZREMRANGEBYSCORE

Last updated 
ZREMRANGEBYSCORE key min max
Group
Sorted set
Complexity
O(log(N)+M) where N is the size of the sorted set and M is the number of members removed
Arity
4 (exactly, counting the command name)
Flags
write
Keys
first 1, last 1, step 1
HotKV Cloud
All plans
On-Premise
no license needed

ZREMRANGEBYSCORE removes every member of the sorted set at key whose score is between min and max. Bounds are inclusive unless prefixed with (, and -inf / +inf are allowed. When the sorted set becomes empty, the key is deleted.

A common use is trimming time-ordered data, for example removing entries whose score (a timestamp) is older than a cutoff.

Return value

Section titled “Return value”
Case RESP2 RESP3
Success Integer: the number of members removed Same
Key does not exist Integer 0 Same

Errors:

  • ERR min or max is not a float for a bad bound. The bounds are checked before the key is looked up.
  • WRONGTYPE if key holds a value that is not a sorted set.

Examples

Section titled “Examples”
127.0.0.1:6379> ZADD events 1700000000 "e1" 1700000100 "e2" 1700000200 "e3"
(integer) 3
127.0.0.1:6379> ZREMRANGEBYSCORE events -inf (1700000150
(integer) 2
127.0.0.1:6379> ZRANGE events 0 -1
1) "e3"

Compatibility

Section titled “Compatibility”

Same as Redis 7.4 and Valkey 8.

See also

Section titled “See also”

ZREMRANGEBYRANK, ZREMRANGEBYLEX, ZCOUNT, ZREM