summaryrefslogtreecommitdiffstats
path: root/iredis/data/commands/save.md
diff options
context:
space:
mode:
Diffstat (limited to 'iredis/data/commands/save.md')
-rw-r--r--iredis/data/commands/save.md9
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.