Use RPUSHX to add elements to the tail of a list only when the list already exists.
Nothing happens and the reply is 0 when the key does not exist, and no key is created. Use it when producers should append to a queue only while it is alive, for example when the list is created by a consumer that is currently attached, so that writes to a queue nobody is reading do not silently pile up.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
<element> | Yes | Yes | Element to push. |
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.