0

Remove vacuum_db_post_upgrade for v32

This version doesn't seem to do tasks to save DB space, like compression
or JSON -> Proto conversion, and the vacuum operation can slow upgrade.

Change-Id: I0b0bd73b29c64afe78f200bc4098133e4cb683c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6276349
Commit-Queue: Qingxin Wu <qingxinwu@google.com>
Reviewed-by: Qingxin Wu <qingxinwu@google.com>
Auto-Submit: Caleb Raitto <caraitto@chromium.org>
Commit-Queue: Caleb Raitto <caraitto@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1421433}
This commit is contained in:
Caleb Raitto
2025-02-18 09:05:50 -08:00
committed by Chromium LUCI CQ
parent d9db75a5e2
commit 1fa15ef738

@ -3111,7 +3111,6 @@ bool UpgradeDB(sql::Database& db,
// Conversion is a no-op, just bookkeeping for a proto change.
[[fallthrough]];
case 31:
vacuum_db_post_upgrade = true;
if (!UpgradeV31SchemaToV32(db, meta_table)) {
return false;
}