| From: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
|---|---|
| To: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
| Cc: | Nikolay Samokhvalov <nik(at)postgres(dot)ai>, Andrei Lepikhov <lepihov(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Dave Page <dpage(at)pgadmin(dot)org>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Wang Cheng <348448708(at)qq(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Proposal: Job Scheduler |
| Date: | 2025-06-01 08:27:27 |
| Message-ID: | 5B574238-1F51-452B-9A2E-1C6C93468C51@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 30 May 2025, at 5:24 PM, Adam Brusselback <adambrusselback(at)gmail(dot)com> wrote:
>
> Add me to the +1 for having a built-in scheduler. It's useful for plenty of things like automated partition creation (as noted), scheduling backups, index maintenance, batch processing jobs, etc...
>
> I wrote jpgAgent (compatible with pgAgent) ~10 years ago because pgAgent was too unstable (and the other scheduling tools hadn't come out yet), but I really wish I didn't have to deal with external tooling for features like this at all.
I could see an argument of adopting pg_cron as a contrib/ module to the core;
not only because it’s become the standard, but it’s a nice example of an extension using bgworker.
But having it in core? I don’t think so; It’s way beyond the scope of an RDBMS,
which already has transactions and SKIP LOCKED, and I think that’s as fast as it should go.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2025-06-01 08:34:49 | pgsql: postgres_fdw: Inherit the local transaction's access/deferrable |
| Previous Message | Joel Jacobson | 2025-06-01 06:24:31 | Re: Missing pg_depend entries for constraints created by extensions (deptype 'e') |