LASTSAVE(3valkey)
πΎ LASTSAVE β the "when did we last actually save tho" command (valkey manual, 3valkey)
okay bestie sit DOWN because this one is tiny but iconic. it's the Valkey Command Manual entry for LASTSAVE, and it's giving "small but mighty" energy fr fr. β¨
π NAME π
lastsave β hands you the Unix timestamp of the last successful save to disk. that's it. that's the whole job. π
β¨ SYNOPSIS β¨
LASTSAVE
no args. no flags. no drama. she just exists. π¦
π DESCRIPTION π
Returns the UNIX TIME of the last DB save that actually executed successfully. no cap, "successfully" is doing a lot of work in that sentence, so pay attention.
so here's the glow-up plan if you're a client who wants to know whether a valkey-bgsave(7) BGSAVE command succeeded: you read the LASTSAVE value first, then you issue a BGSAVE command, and then you just... check back at regular intervals, every N seconds, to see if LASTSAVE changed. if it moved, the save went through. if it's frozen, it did not. periodt. π
and one more thing that's lowkey important: Valkey considers the database saved successfully at startup. so that first value isn't from a save you did β it's just how she wakes up. π
π¬ REPLY π¬
valkey-protocol(7) Integer reply: the UNIX TIME of the last DB save that executed with success. a whole integer. that's the reply. slay. π
β‘ COMPLEXITY β‘
O(1) β constant time, bestie. she does not care how big your dataset is. iconic behavior honestly. π₯
π ACL CATEGORIES π
@admin @dangerous @fast
yeah she's in the dangerous club. she's also fast. both things can be true. π
π HISTORY π
- Available since:
1.0.0
an OG. she's been here since the beginning and she's not leaving. π
π SEE ALSO π
the whole extended friend group, no one left out:
acl(3valkey)acl-cat(3valkey)acl-deluser(3valkey)acl-dryrun(3valkey)acl-genpass(3valkey)acl-getuser(3valkey)acl-help(3valkey)acl-list(3valkey)acl-load(3valkey)acl-log(3valkey)acl-save(3valkey)acl-setuser(3valkey)acl-users(3valkey)acl-whoami(3valkey)bgrewriteaof(3valkey)bgsave(3valkey)command(3valkey)command-count(3valkey)command-docs(3valkey)command-getkeys(3valkey)command-getkeysandflags(3valkey)command-help(3valkey)command-info(3valkey)command-list(3valkey)commandlog(3valkey)commandlog-get(3valkey)commandlog-help(3valkey)commandlog-len(3valkey)commandlog-reset(3valkey)config(3valkey)config-get(3valkey)config-help(3valkey)config-resetstat(3valkey)config-rewrite(3valkey)config-set(3valkey)dbsize(3valkey)debug(3valkey)failover(3valkey)flushall(3valkey)flushdb(3valkey)info(3valkey)latency(3valkey)latency-doctor(3valkey)latency-graph(3valkey)latency-help(3valkey)latency-histogram(3valkey)latency-history(3valkey)latency-latest(3valkey)latency-reset(3valkey)lolwut(3valkey)memory(3valkey)memory-doctor(3valkey)memory-help(3valkey)memory-malloc-stats(3valkey)memory-purge(3valkey)memory-stats(3valkey)memory-usage(3valkey)module(3valkey)module-help(3valkey)module-list(3valkey)module-load(3valkey)module-loadex(3valkey)module-unload(3valkey)monitor(3valkey)psync(3valkey)replconf(3valkey)replicaof(3valkey)restore-asking(3valkey)role(3valkey)save(3valkey)shutdown(3valkey)slowlog(3valkey)slowlog-get(3valkey)slowlog-help(3valkey)slowlog-len(3valkey)slowlog-reset(3valkey)swapdb(3valkey)sync(3valkey)time(3valkey)
ngl the whole point of this command is the vibe check: read it, run BGSAVE, read it again every N seconds, see if the number moved. that's the technique. iykyk. π
okay that's the whole page, bestie, you ate it. π«Ά this was the Valkey manual, version 9.0.0, dated 2025-10-21, filed under LASTSAVE(3valkey). go forth and timestamp responsibly. πβ¨π
π¦ where this page comes from
- fedora 44: valkey-doc 9.0.3-2.fc44 Β· CC-BY-SA-4.0
- fedora 44: valkey-doc 9.0.6-1.fc44 Β· CC-BY-SA-4.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms