diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2023-01-04 07:19:32 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2023-01-04 07:19:32 +0000 |
| commit | 7480e618ec785ba8a1c74c8a150cffe5880fb3bb (patch) | |
| tree | 87422376dd9a7eee55850f0fce9a8bb4c13e44a2 /iredis/data/commands/save.md | |
| parent | Adding upstream version 1.12.1. (diff) | |
| download | iredis-7480e618ec785ba8a1c74c8a150cffe5880fb3bb.tar.xz iredis-7480e618ec785ba8a1c74c8a150cffe5880fb3bb.zip | |
Adding upstream version 1.13.0.upstream/1.13.0
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'iredis/data/commands/save.md')
| -rw-r--r-- | iredis/data/commands/save.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/iredis/data/commands/save.md b/iredis/data/commands/save.md index 540dc7a..c66c5e9 100644 --- a/iredis/data/commands/save.md +++ b/iredis/data/commands/save.md @@ -3,10 +3,11 @@ _point in time_ snapshot of all the data inside the Redis 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 Redis 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. +block all the other clients. +Instead usually `BGSAVE` is used. +However in case of issues preventing Redis 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][tp] for detailed information. |