Use ZREMRANGEBYSCORE to remove the members of a sorted set whose score falls in a range.
Bounds are inclusive by default, become exclusive when prefixed with (, and accept -inf and +inf. The reply is the number of members removed, and the key is deleted when it becomes empty.
With timestamps as scores this is how a sliding window is maintained: drop everything older than the cutoff in one call, which is exactly what a sorted-set rate limiter does before counting what is left.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
<min> | Yes | No | Minimum score: a number, -inf, or (score for an exclusive bound. |
<max> | Yes | No | Maximum score: a number, +inf, or (score for an exclusive bound. |
Response#
The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
| Protocol | Reply |
|---|---|
| RESP2 | Integer |
| RESP3 | Integer |
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
Examples#
TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.