public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrei Lepikhov <[email protected]>
To: Nikolay Samokhvalov <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Dave Page <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: Wang Cheng <[email protected]>
Cc: pgsql-hackers <[email protected]>
Cc: Dmitry Dolgov <[email protected]>
Subject: Re: Proposal: Job Scheduler
Date: Fri, 30 May 2025 11:22:31 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAM527d_cOMW9jde9_2SE+LWOHNi+o7KBdNpLTPyy3XqwZCVQ1g@mail.gmail.com>
References: <CA+OCxowP067JcwXbtKTV=8Xh+grC+KLgHkL6POnYY0A92eVEoA@mail.gmail.com>
	<[email protected]>
	<sjagfbmbdmarpa6k7r3xf3o65as5onlbwje4uqhotsa4emknwh@5jdpe234pcs2>
	<CAM527d_cOMW9jde9_2SE+LWOHNi+o7KBdNpLTPyy3XqwZCVQ1g@mail.gmail.com>

On 5/30/25 03:17, Nikolay Samokhvalov wrote:
> On Thu, Jun 6, 2024 at 5:31 AM Dmitry Dolgov <[email protected] 
>     +1. The PostgreSQL ecosystem is surprisingly fragmented, when it comes
>     to quite essential components that happen to be outside of the core. But
>     of course it doesn't mean that there should be _one_ component of every
>     kind in core, more like it makes sense to have _one_ component available
>     out of the box (where the box is whatever form of PostgreSQL that gets
>     delivered to users, e.g. a distro package, container, etc.).
> 
> 
> +1 too.
> 
> There is a huge reason to have a job scheduler in core – new partition 
> creation.
> 
> In my opinion, partitioning in Postgres needs more automation, and new 
> partition creation is a big missing piece. And it does require a scheduler.
> 
> I like pg_timetable a lot, but it's written in Go;
> 
> pg_cron is written in Go, and it's already present in most managed 
> Postgres platforms. Why not to bring it to Postgres core so we could 
> then use it to improve developer experience of dealing with partitioning?
I would say you should provide a reason why it is too difficult to stay 
outside the core, such as pg_hint_plan or a similar feature.
In my opinion, the main reason to push an extension into contrib is if 
it has a strong connection with the core API. But the scheduler seems as 
far from the volatile API features as possible.
That's more, contrib extensions have essential priority to external 
solutions and reduce development impulse in the area.

-- 
regards, Andrei Lepikhov

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Proposal: Job Scheduler
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox