Use PERSIST to remove the expiration from a key so that it stops being deleted automatically and lives until it is removed explicitly.
The reply is 1 when an expiration was removed and 0 when the key does not exist or had no expiration to begin with. This is how a value gets promoted from temporary to permanent without rewriting it, for example when a trial record becomes a persistent one.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
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: 1 if the timeout was removed, 0 otherwise |
| RESP3 | Integer: 1 if the timeout was removed, 0 otherwise |
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.