SAVE
SAVE
- Available since
- 1.0.0
- Time complexity
- O(N) where N is the total number of keys in all databases
- ACL categories
- @admin, @slow, @dangerous
The SAVE
commands performs a synchronous save of the dataset producing a
point in time snapshot of all the data inside the Redict instance, in the form
of an RDB file.
You almost never want to call SAVE
in production environments where it will
block all the other clients.
Instead usually BGSAVE
is used.
However in case of issues preventing Redict to create the background saving child
(for instance errors in the fork(2) system call), the SAVE
command can be a
good last resort to perform the dump of the latest dataset.
Please refer to the persistence documentation for detailed information.