We migrated from a community edition to an Apache instance to help with managed back-ups and it looks like some Timescale jobs were in the backup and transferred over; they seem to run and fail constantly but we don’t seem to have any way of deleting them as alter_job and delete_job are locked on the license.
Any idea how we can stop them running?
Can you try to _stop_background_workers() ?
Check job troubleshooting page: Timescale Documentation | Troubleshooting jobs
Hi,
Use the timescaledb.delete_job Function. If you have access to the TimescaleDB’s internal functions, you can execute SELECT timescaledb.delete_job(job_id) where job_id is the ID of the job you want to delete. This might bypass the license restriction for delete_job.
Thanks
@luisaweber @jonatasdp thanks for getting back to me; its appreciated.
Unfortunately, both of these don’t work in our environment (Digital Ocean Managed).
_stop_background_workers can only be envoked by super-users and delete_job() yields:
ERROR: function “delete_job” is not supported under the current “apache” license
HINT: Upgrade your license to ‘timescale’ to use this free community feature.
I think we may need to reach out to DO and ask them to delete the jobs with their SU account.
Thanks for your help though and let me know if you think of anything else.
Cheers,
Tim at Ping
Yes! The same at Timescale Cloud, or you’d need to restart the service via panel.
Another idea would be find the _timescaledb_internal.job* table that contains the metadata and remove it. Probably it would fall in the same problem that you’d need to be admin.
Have you tried to disable telemetry?