Background
#3298 removed the legacy DBCol::Triple column family, its dual-write, and the
startup migration. To reclaim disk on nodes upgrading from 3.11, SecretDB::new
now drops the on-disk "triple" column family once on startup if present
(crates/node/src/db.rs). This one-time cleanup is only needed until every
production node has run 3.12 at least once, after which no node still carries the
column on disk.
Acceptance Criteria
- Remove the
legacy_triple drop branch in SecretDB::new (crates/node/src/db.rs).
- Remove the
secret_db_new__should_drop_legacy_triple_column_family_on_startup test.
Background
#3298 removed the legacy
DBCol::Triplecolumn family, its dual-write, and thestartup migration. To reclaim disk on nodes upgrading from 3.11,
SecretDB::newnow drops the on-disk
"triple"column family once on startup if present(
crates/node/src/db.rs). This one-time cleanup is only needed until everyproduction node has run 3.12 at least once, after which no node still carries the
column on disk.
Acceptance Criteria
legacy_tripledrop branch inSecretDB::new(crates/node/src/db.rs).secret_db_new__should_drop_legacy_triple_column_family_on_startuptest.