pg_cron partly jobs not running without any logs on job_run_details table.
- Dominant language
- C
- Stars
- 3.9k
- Forks
- 260
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
PostgreSQL version is 11.5.
pg_cron 1.4-1.
OS: Centos 7.9
There are 50 jobs running by pg_cron. But 13 jobs stop unexpected since 2023 01/29.
This table cron.job_run_details also no infomation about those 13 failed jobs.
create new jobs also not running. others old jobs running normally.
This parameter is max_worker_processes=16.
Usually 1-3 jobs running in parallel.
Would you like to guide me resovle this issue ? How to collect infomation to narrow down it.
I don't find any upgrade method to update pg_cron.
How to upgrade pg_cron to new version without impact current jobs ? I mean don't need re-create all jobs. Thanks in advance.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported pg_cron 1.4-1 behavior on PostgreSQL 11.5, focusing on cron.job_run_details and the max_worker_processes=16 setting. Reproduce or narrow down why some existing and newly created jobs do not run, and document diagnostic evidence and a safe upgrade path that preserves current jobs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, postgresql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100