Files
cc-backend/.entire/metadata/42401d2e-7d1c-4c0e-abe6-356cb2d48747/prompt.txt
Jan Eitzinger eba3995610 Add Analyse on db startup
Entire-Checkpoint: ea70a955214d
2026-03-11 05:28:52 +01:00

1 line
317 B
Plaintext

There also have to be bugs in jobQuery.go . Especially the following query triggers the memory leak: SELECT * FROM job WHERE job.job_state IN ("completed", "running", "failed") ORDER BY job.start_time DESC LIMIT 1 OFFSET 10; Dig deeper to find the cause. Also investigate why no existing index is used for this query.