115/118: Disable vacuuming the DB after garbage collection

[Ludovic Court�s]

civodul pushed a commit to branch nix
in repository guix.

commit 554eaf5e8c82ddd6a42e4301f6d3dd5419c04060
Author: Eelco Dolstra <eelco.dols...@logicblox.com>
Date:   Wed Nov 19 18:02:39 2014 +0100

    Disable vacuuming the DB after garbage collection
    
    Especially in WAL mode on a highly loaded machine, this is not a good
    idea because it results in a WAL file of approximately the same size
    ad the database, which apparently cannot be deleted while anybody is
    accessing it.
---
 nix/libstore/gc.cc |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/nix/libstore/gc.cc b/nix/libstore/gc.cc
index e019d93..f98e02c 100644
--- a/nix/libstore/gc.cc
+++ b/nix/libstore/gc.cc
@@ -724,7 +724,7 @@ void LocalStore::collectGarbage(const GCOptions & options, 
GCResults & results)
     }
 
     /* While we're at it, vacuum the database. */
-    if (options.action == GCOptions::gcDeleteDead) vacuumDB();
+    //if (options.action == GCOptions::gcDeleteDead) vacuumDB();
 }