History Archive Era

Scope

A single day, 2026-04-06. Four commits introduce the database backup script, the archive-tables migration, and the actual archive runs for inactive and non-AB companies.

This era is data lifecycle work — moving cold rows out of hot tables.

Commits

4deddb7 — 2026-04-06 — feat: add database backup script and archive tables migration for inactive companies

Sparse body. Adds the backup script and the migration that creates archive tables (likely migrations/007_add_archive_tables.sql — later renamed to 009 in commit 81c2568; see History Migrations Era).

1c6f2dc — 2026-04-06 — feat: add archive verification, archive-inactive, and restore-from-archive scripts

Sparse body. Three operational scripts:

• archive verification — sanity check that an archive run completed correctly.
• archive-inactive — the actual move job for inactive companies.
• restore-from-archive — the inverse, for restoring archived rows back to hot tables.

15f01d8 — 2026-04-06 — feat: archive inactive companies - 2026-04-06

The actual archive run for inactive companies. The dated suffix on the message implies this is a one-off archive event, not a feature commit.

8ea0a44 — 2026-04-06 — feat: archive non-AB companies - 2026-04-06

Same shape — the second archive run, this one for non-AB legal forms.

87a0bea — 2026-04-06 — docs: add archive validation report

The validation report for the two archive runs above. Lives in repo docs.

Verify the contents of the archive validation report ( docs/?). The commit message does not include the path. Purpose unclear from message alone — likely lists how many rows were archived per table and any inconsistencies caught.

Significance

• Hot-table size dropped after these commits. Counts not in the commit messages — see the validation report referenced in 87a0bea for the actual numbers.
• The archive infrastructure is reusable: the migration creates tables, scripts move rows, restore reverses. Future archive runs (e.g. quarterly) can re-use the scripts.
• Commit 81c2568 (2026-04-27) renamed 007_add_archive_tables.sql to 009_add_archive_tables.sql to resolve a numbering collision with 007_pgvector_company_embeddings.sql. Anyone scripting against the migration filename should be aware.

See also

History Migrations Era, Schema Migrations, Database Schema, History Overview.

See also

• History MOC