• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

zentralopensource / zentral / 32471090911
92%

Build:
DEFAULT BRANCH: main
Ran 21 Aug 2026 10:15AM UTC
Jobs 1
Files 1030
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

21 Aug 2026 09:48AM UTC coverage: 90.0% (+0.01%) from 89.986%
32471090911

push

github

np5
inventory: delete the cleanup orphans and history in bounded batches

Every table was purged with a single unbounded DELETE, so one transaction
could remove millions of rows and hand the whole backlog of dead tuples to
autovacuum at once. Most of that volume never appears in the statements:
the archived machine snapshots cascade into twelve child tables, and the
biggest of them is orders of magnitude larger than the snapshots themselves.
The database could sit at its capacity ceiling for as long as the job ran.

The deletes are batched on the primary key of the table now, so that each
transaction is bounded and autovacuum can keep pace between the batches. The
batch resumes on the key it stopped at instead of applying a plain LIMIT to
the anti join, which would rescan the table from the start on every
iteration. The cutoffs used to trim the machine snapshot commit history are
computed once into a temporary table, for the same reason: the aggregate
scanned the whole table, and one batch per statement would have repeated it.
A commit added while the batches run only makes the frozen cutoff older than
a fresh aggregate would give, so the newest commit of a machine is still
never deleted. That history is deleted from the highest id down, because a
commit is always more recent than its parent, and deleting the children
first spares the ON DELETE SET NULL updates on rows a later batch deletes
anyway.

The retries after an integrity error now apply to the batch instead of
restarting the whole table, and report through the logger rather than
print(), which bypassed the quiet flag of the management command. A table
that could not be purged reports the rows it did delete.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

50 of 50 new or added lines in 1 file covered. (100.0%)

51029 of 56699 relevant lines covered (90.0%)

0.9 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32471090911.1 21 Aug 2026 10:15AM UTC 1030
90.0
GitHub Action Run
Source Files on build 32471090911
  • Tree
  • List 1030
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #32471090911
  • 20bffaa2 on github
  • Prev Build on main (#32469010472)
  • Next Build on main (#32472025722)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc