ClusterCockpit/cc-backend
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-backend synced 2026-03-15 12:27:30 +01:00
Code Issues Packages Releases Activity

Add migration with alternative reduces index set

Browse Source 
Entire-Checkpoint: af7afc9a29ff
This commit is contained in:
Jan Eitzinger
2026-03-11 05:46:03 +01:00
parent eba3995610
commit 301e590580
7 changed files with 551 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.entire/metadata/42401d2e-7d1c-4c0e-abe6-356cb2d48747/prompt.txt
View File

@@ -1 +1 @@
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.
What optimal index selection do you suggest? The job table contains almost 20 million jobs in production causing timouts on any filter query that does not use and index.