From ca37e9cde814dd093cf2cf5d36f178854d768b3e Mon Sep 17 00:00:00 2001
From: antirez <antirez@gmail.com>
Date: Wed, 22 Apr 2009 01:44:48 +0200
Subject: [PATCH] FLUSHALL/FLUSHDB no longer sync on disk. Just increment the
 dirty counter by the number of elements removed, that will probably trigger a
 background saving operation

---
 redis.c | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/redis.c b/redis.c
index 7c382af7..e74910ba 100644
--- a/redis.c
+++ b/redis.c
@@ -875,13 +875,16 @@ static void initServer() {
 }
 
 /* Empty the whole database */
-static void emptyDb() {
+static long long emptyDb() {
     int j;
+    long long removed = 0;
 
     for (j = 0; j < server.dbnum; j++) {
+        removed += dictSize(server.db[j].dict);
         dictEmpty(server.db[j].dict);
         dictEmpty(server.db[j].expires);
     }
+    return removed;
 }
 
 /* I agree, this is a very rudimental way to load a configuration...
@@ -3038,18 +3041,17 @@ static void sunionstoreCommand(redisClient *c) {
 }
 
 static void flushdbCommand(redisClient *c) {
+    server.dirty += dictSize(c->db->dict);
     dictEmpty(c->db->dict);
     dictEmpty(c->db->expires);
-    server.dirty++;
     addReply(c,shared.ok);
-    rdbSave(server.dbfilename);
 }
 
 static void flushallCommand(redisClient *c) {
-    emptyDb();
-    server.dirty++;
+    server.dirty += emptyDb();
     addReply(c,shared.ok);
     rdbSave(server.dbfilename);
+    server.dirty++;
 }
 
 redisSortOperation *createSortOperation(int type, robj *pattern) {