fix(db): add time_sensitive to oc_jobs index for maintenance window performance

[turanalmammadov]

Fixes #46126

Problem

The background job scheduler uses this query to pick the next job:

SELECT * FROM oc_jobs
WHERE reserved_at <= ?
  AND last_checked <= ?
  AND time_sensitive = ?
ORDER BY last_checked ASC
LIMIT ?

The old index job_lastcheck_reserved only covered (last_checked, reserved_at). The database had to do a partial index scan and then fetch each row individually to evaluate time_sensitive = ?. Under load with a maintenance window this causes many unnecessary I/O operations since most rows are excluded by the time_sensitive condition.

Solution

Drop job_lastcheck_reserved and replace it with job_lastcheck_timesens on (last_checked, reserved_at, time_sensitive). Because the query's WHERE columns are now all in the index the database can use a covering index scan, evaluating the time_sensitive predicate without reading any data rows.

Changes

1. New DB migration

core/Migrations/Version33000Date20260224000000.php

• Drops old index job_lastcheck_reserved
• Creates new index job_lastcheck_timesens with all three columns

2. AddMissingIndicesListener update

core/Listener/AddMissingIndicesListener.php

• Updated to reference the new index name and columns
• Ensures occ db:add-missing-indices repairs existing installations

Impact

• Faster cron execution, especially when a maintenance window is active
• Reduces database I/O during background job scheduling
• No functional change — index covers the same query that already existed

Made with Cursor

[artonge]

Hey @turanalmammadov, thanks for the pull request, and thanks for being transparent with your usage of AI.

Can you double-check that this won't impact other request negatively? I don't know if such requests exist, but we might have some that do not include the time sensitive filter, and if so, I think those requests won't be able to use the index anymore.

Also, can you share more regarding the actual impact in terms of numbers? How many rows do you have in your oc_jobs table, and how much time it takes to run the query with and without your changes?