> On 30 May 2025, at 5:24 PM, Adam Brusselback <adambrusselb...@gmail.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.
