From: | Wang Cheng <348448708(at)qq(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Proposal: Job Scheduler |
Date: | 2024-06-06 08:27:14 |
Message-ID: | tencent_C2E1296B66E5225EA7158B2F0E396401CB09@qq.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hackers,
We are the PostgreSQL team in Tencent. We have recently developed a job scheduler that runs inside the database to schedules and manages jobs similar to Oracle DBMS_JOB package, and we would like to contribute this feature to the community.
Similar to autovacuum, the job scheduler consists of 2 parts: the job launcher and the job worker. The job launcher periodically scans a metadata table and signals the postmaster to start new workers if needed.
As far as we know, there are currently two open-sourced job scheduling extensions for PostgreSQL: pg_cron (https://github.com/citusdata/pg_cron/) and pg_dbms_job (https://github.com/MigOpsRepos/pg_dbms_job/tree/main) However, the cron-based syntax is not easy to use and suffers some limitations like one-off commands. The pg_dbms_job extension is difficult to manage and operate because it runs as a standalone process .
That's why we have developed the job scheduler that runs as a process inside the database just like autovacuum.
We can start to send the patch if this idea makes sense to the you. Thanks for your time.
Regards,
Cheng
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-06-06 08:47:35 | Re: Proposal: Job Scheduler |
Previous Message | Hannu Krosing | 2024-06-06 08:25:26 | Re: question regarding policy for patches to out-of-support branches |