diff options
| author | Eelco Dolstra <eelco.dolstra@logicblox.com> | 2014-11-19 18:02:39 +0100 |
|---|---|---|
| committer | Ludovic Courtès <ludo@gnu.org> | 2015-05-11 17:42:18 +0200 |
| commit | 554eaf5e8c82ddd6a42e4301f6d3dd5419c04060 (patch) | |
| tree | 45551eda6acb6a06e859107fae021fd20fcd7fc4 | |
| parent | 4eb62b5230c29e2f6ab17352439521083846c259 (diff) | |
| download | guix-554eaf5e8c82ddd6a42e4301f6d3dd5419c04060.tar.gz | |
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.
| -rw-r--r-- | 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 e019d9343e..f98e02c1e2 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(); } |