Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Subject: Re: Proposal: Job Scheduler
From: Florents Tselai <florents.tselai@gmail.com>
In-Reply-To: 
 <CAMjNa7cj_t1+mh9Lx8W3Hobfqcn-S0D9J5BxuPpXeWr2mJzgLA@mail.gmail.com>
Date: Sun, 1 Jun 2025 11:27:27 +0300
Cc: Nikolay Samokhvalov <nik@postgres.ai>,
 Andrei Lepikhov <lepihov@gmail.com>,
 =?utf-8?Q?=C3=81lvaro_Herrera?= <alvherre@alvh.no-ip.org>,
 Dave Page <dpage@pgadmin.org>,
 Dmitry Dolgov <9erthalion6@gmail.com>,
 Laurenz Albe <laurenz.albe@cybertec.at>,
 Wang Cheng <348448708@qq.com>,
 pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B574238-1F51-452B-9A2E-1C6C93468C51@gmail.com>
References: 
 <CA+OCxowP067JcwXbtKTV=8Xh+grC+KLgHkL6POnYY0A92eVEoA@mail.gmail.com>
 <202406061053.nrg23pctc6wm@alvherre.pgsql>
 <sjagfbmbdmarpa6k7r3xf3o65as5onlbwje4uqhotsa4emknwh@5jdpe234pcs2>
 <CAM527d_cOMW9jde9_2SE+LWOHNi+o7KBdNpLTPyy3XqwZCVQ1g@mail.gmail.com>
 <1763c6c6-cf71-4e64-bd47-0451c5334358@gmail.com>
 <CAM527d-9GANWpHspLGiCSWKo=dL5Uj__kHM1kJ84POcS=v0yYQ@mail.gmail.com>
 <CAMjNa7cj_t1+mh9Lx8W3Hobfqcn-S0D9J5BxuPpXeWr2mJzgLA@mail.gmail.com>
To: Adam Brusselback <adambrusselback@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/5B574238-1F51-452B-9A2E-1C6C93468C51%40gmail.com>
Precedence: bulk


> On 30 May 2025, at 5:24=E2=80=AFPM, Adam Brusselback =
<adambrusselback@gmail.com> wrote:
>=20
> 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...
>=20
> 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=E2=80=99s become the standard, but it=E2=80=99s a =
nice example of an extension using bgworker.

But having it in core? I don=E2=80=99t think so; It=E2=80=99s way beyond =
the scope of an RDBMS,
which already has transactions and SKIP LOCKED, and I think that=E2=80=99s=
 as fast as it should go.=