diff options
| author | Eelco Dolstra <eelco.dolstra@logicblox.com> | 2014-11-19 18:02:39 +0100 |
|---|---|---|
| committer | Eelco Dolstra <eelco.dolstra@logicblox.com> | 2014-11-19 18:14:24 +0100 |
| commit | 8299aaf07988a3ca7ecda3526b7e25a885550db5 (patch) | |
| tree | 955f64f933f4330df2e44f6b1e589d06a6506103 | |
| parent | a3e5c99d66e111455c6ddc40759005718016c8dd (diff) | |
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-- | src/libstore/gc.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libstore/gc.cc b/src/libstore/gc.cc index 0806430ef..49cb11d23 100644 --- a/src/libstore/gc.cc +++ b/src/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(); } |