git-echo/linux_patch_manager
Private
Public Access
1
0
Fork 0
Code Releases 8 Wiki Activity

fix: patch poller UPSERT and host_patch_data unique constraint
Some checks failed
CI Pipeline / Rust Format Check (push) Has been cancelled
Details
CI Pipeline / Clippy Lints (push) Has been cancelled
Details
CI Pipeline / Rust Unit Tests (push) Has been cancelled
Details
CI Pipeline / Security Audit (push) Has been cancelled
Details
CI Pipeline / Frontend Lint & Type Check (push) Has been cancelled
Details
CI Pipeline / Build .deb & Release (push) Has been cancelled
Details

Browse Source 
BUG-14: Patch poller was INSERT-ing a new row every poll cycle instead of
UPSERT-ing, creating 51 duplicate rows in host_patch_data for a single host.

Changes:
- patch_poller.rs: Changed INSERT to INSERT...ON CONFLICT (host_id) DO UPDATE
  so each host only has one row that gets updated on each poll
- Migration 006: Added UNIQUE constraint on host_id, cleaned up 50 duplicate
  rows keeping only the latest polled_at per host

The dashboard showing 174 pending patches and 0% compliance is expected
behavior - the patch data was collected before the job ran and the poller
runs every 30 minutes. The next poll cycle will refresh the data.
This commit is contained in:
Echo
2026-04-30 01:11:23 +00:00
parent ec88a52be2
commit 2a9c6e8ed3
2 changed files with 19 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
migrations/006_host_patch_data_unique.sql Normal file
View File

@ -0,0 +1,12 @@
-- Migration 006: Add UNIQUE constraint on host_id in host_patch_data
-- Clean up duplicate rows (keep latest polled_at per host) before adding constraint.
-- Step 1: Delete duplicate rows, keeping only the most recent poll per host
DELETE FROM host_patch_data a
USING host_patch_data b
WHERE a.host_id = b.host_id
AND a.polled_at < b.polled_at;
-- Step 2: Add UNIQUE constraint on host_id
ALTER TABLE host_patch_data
ADD CONSTRAINT host_patch_data_host_id_key UNIQUE (host_id);