Back to Redis

PEXPIREAT

content/commands/pexpireat.md

latest2.0 KB
Original Source

PEXPIREAT has the same effect and semantic as [EXPIREAT]({{< relref "/commands/expireat" >}}), but the Unix time at which the key will expire is specified in milliseconds instead of seconds.

Options

The PEXPIREAT command supports a set of options since Redis 7.0:

  • NX -- Set expiry only when the key has no expiry
  • XX -- Set expiry only when the key has an existing expiry
  • GT -- Set expiry only when the new expiry is greater than current one
  • LT -- Set expiry only when the new expiry is less than current one

A non-volatile key is treated as an infinite TTL for the purpose of GT and LT. The GT, LT and NX options are mutually exclusive.

Examples

{{% redis-cli %}} SET mykey "Hello" PEXPIREAT mykey 1555555555005 TTL mykey PTTL mykey {{% /redis-cli %}}

Redis Software and Redis Cloud compatibility

| Redis Software | Redis Cloud | <span style="min-width: 9em; display: table-cell">Notes</span> | |:----------------------|:-----------------|:------| | <span title="Supported">✅ Standard</span> <span title="Supported"><nobr>✅ Active-Active</nobr></span> | <span title="Supported">✅ Standard</span> <span title="Supported"><nobr>✅ Active-Active</nobr></span> | |

Return information

{{< multitabs id="pexpireat-return-info" tab1="RESP2" tab2="RESP3" >}}

One of the following:

  • Integer reply: 1 if the timeout was set.
  • Integer reply: 0 if the timeout was not set. For example, if the key doesn't exist, or the operation was skipped due to the provided arguments.

-tab-sep-

One of the following:

  • Integer reply: 1 if the timeout was set.
  • Integer reply: 0 if the timeout was not set. For example, if the key doesn't exist, or the operation was skipped due to the provided arguments.

{{< /multitabs >}}