38879323205
91%

Ran 16 Oct 2026 09:28AM UTC

Jobs 1

Files 1035

Run time 1min

Badge

Embed ▾

Committed 16 Oct 2026 09:04AM UTC coverage: 90.932%. Remained the same

Build # 38879323205

Build Type

push

github

Committed by

np5

Commit Message

santa: use no target id for an existing target

The event upload inserts all its targets with ON CONFLICT DO NOTHING.
PostgreSQL gets the next value of the id sequence for each row before
it finds the conflict. So each upload used one id for each target it
reported, also for the targets that already existed. The id is an
integer: when the sequence reaches 2147483647, every insert into
santa_target fails, and every event upload fails with it.

The two inserts of the event upload skip the existing targets with a
NOT EXISTS filter now. Two uploads that insert the same new target at
the same time can still use one id more. ON CONFLICT DO NOTHING stays
for that case, and the inserts stay sorted.

The filter adds one index lookup for each new target. In a test on a
table of 4 million targets, with 50, 500 and 5000 targets for each
insert, the plan is a nested loop anti join on the (type, identifier)
unique index, and the insert reads no more pages than before.

When update_target_counters is true, the target counter upsert still
uses one santa_targetcounter id for each target of each upload.

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

Coverage Stats

52916 of 58193 relevant lines covered (90.93%)

0.91 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	38879323205.1	16 Oct 2026 09:27AM UTC	1035	90.93	GitHub Action Run

zentralopensource / zentral / 38879323205
91%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 38879323205

zentralopensource / zentral / 38879323205 91%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 38879323205

zentralopensource / zentral / 38879323205
91%

README BADGES
x