RESTORE

v0.1.0-beta.1 · Tested in Docker · 2026-09-21

Creates a key from a serialized value.

Keys & expiration · Example verified

Syntax covered here

RESTORE key ttl serialized-value

The verified round trip uses a DUMP payload and ttl 0, meaning no expiry; GET confirms the restored string.

Tested example & replies

Requests below run in order against an empty database. Each connection authenticates with the fixture password first. Quoted values are strings; null is a nil reply; arrays preserve RESP order.

# connection: default
> SET sample value
"OK"
# connection: default
> DUMP sample
{"base64":"AAV2YWx1ZQsA6Cl8Szw1cuc=","bytes":17}
# Capture these exact bytes as payload.
# connection: default
> RESTORE restored 0 <captured:payload>
"OK"
# connection: default
> GET restored
"value"

A captured marker refers to raw bytes returned by an earlier request, not a literal string to type. Binary replies are displayed as Base64; the executable test passes the original bytes unchanged.

Verification scope: the argument forms, setup and assertions shown here. These examples do not establish support for unlisted options or deployment modes. Run your application tests with your data and client.

Test environment & reproducible evidence

Verified: 2026-09-21T11:06:06Z · Docker / Linux aarch64 · lavik 0.1.0-beta.1

Storage & connection: io_uring · temporary file, 2 workers, standalone, plaintext TCP, password authentication. This test does not measure NVMe performance.

Pinned source: 3955b98d43b312324aa8d52775df52cfb111c0d0

Binary SHA-256: 8306b37ddf05023f85166a6aa2192b7084757e8defd342b602e6470244aca887

Image: sha256:af0cfb11b78f184cb6cc49a774a49dc97a8e43a0bd3f4d63d83c8c9ef3282d6e

Full test receipt · Executable tests

Lavik command registry · Valkey counterpart (support may differ)