summaryrefslogtreecommitdiffstats
path: root/iredis/data/commands/save.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2020-03-21 10:28:17 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2021-02-07 11:16:53 +0000
commit06cba6ccd165ca8b224797e37fccb9e63f026d77 (patch)
treee82f1bc439997ae296f2e74f8a64d84c5d95f140 /iredis/data/commands/save.md
parentInitial commit. (diff)
downloadiredis-06cba6ccd165ca8b224797e37fccb9e63f026d77.tar.xz
iredis-06cba6ccd165ca8b224797e37fccb9e63f026d77.zip
Adding upstream version 1.9.1.upstream/1.9.1
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.md17
1 files changed, 17 insertions, 0 deletions
diff --git a/iredis/data/commands/save.md b/iredis/data/commands/save.md
new file mode 100644
index 0000000..540dc7a
--- /dev/null
+++ b/iredis/data/commands/save.md
@@ -0,0 +1,17 @@
+The `SAVE` commands performs a **synchronous** save of the dataset producing a
+_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.
+
+Please refer to the [persistence documentation][tp] for detailed information.
+
+[tp]: /topics/persistence
+
+@return
+
+@simple-string-reply: The commands returns OK on success.