Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
state
is not set tocode
on the AutoVacuum Job Queueir.cron
data record, so the default actionobject_write
is assigned to it on creation, as a result, the cron job does nothing when it runs (jobs older than 30 days are not being deleted).Affected versions: 12.0, this was already fixed for 11.0 in #112
I've also added a test case and a migration to update the record for existing installations (since the record is marked as
noupdate="1"
).If, like me, you did not notice it for quite a while and now have hundreds of thousands of old jobs (or even more), running the fixed autovacuum cron job will most likely fail due to memory error or a timeout (depends on the setup, of course). To work around that, I've copied the original AutoVacuum Job Queue cron job record and used this for
code
:and setup to run this Cron job e.g. every 5 minutes to clear away the build-up.