Andrey Antukh 0947e666c0 🐛 Keep objects-gc running past a blocked chunk ...

objects-gc deleted every kind of object inside one transaction per proc,
looping until empty, so a single row that a foreign key still references
aborted the whole run: the task died on its first file every night, after
the earlier steps had already spent around twenty minutes. The per-file
savepoint only saved the files proc and left the same shape everywhere
else.

Now every proc streams its pending keys with db/plan inside a read-only
transaction of its own and deletes them chunk by chunk, each chunk in a
transaction of its own with FOR UPDATE SKIP LOCKED. A chunk that fails is
reported with l/err and skipped, so the run reaches the end and the next
run retries the skipped rows.

AI-assisted-by: muse-spark-1.3-contributor

2026-10-13 14:33:32 +02:00

..

backend_tests

🐛 Keep objects-gc running past a blocked chunk

2026-10-13 14:33:32 +02:00

e2e

🐛 Escape LDAP filter values and use directory email in retrieve-user (#11085)

2026-09-10 16:39:35 +02:00