> On 30 May 2025, at 5:24 PM, Adam Brusselback
> 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 (compat
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 o
On Fri, May 30, 2025 at 02:22 Andrei Lepikhov wrote:
> On 5/30/25 03:17, Nikolay Samokhvalov wrote:
> > On Thu, Jun 6, 2024 at 5:31 AM Dmitry Dolgov <9erthali...@gmail.com
> > +1. The PostgreSQL ecosystem is surprisingly fragmented, when it
> comes
> > to quite essential components that h
On 5/30/25 03:17, Nikolay Samokhvalov wrote:
On Thu, Jun 6, 2024 at 5:31 AM Dmitry Dolgov <9erthali...@gmail.com
+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 t
On Thu, May 29, 2025 at 6:17 PM Nikolay Samokhvalov wrote:
> 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 mean, in C, of co
On Thu, Jun 6, 2024 at 5:31 AM Dmitry Dolgov <9erthali...@gmail.com> wrote:
> > On Thu, Jun 06, 2024 at 12:53:38PM GMT, Alvaro Herrera wrote:
> > On 2024-Jun-06, Dave Page wrote:
> >
> > > It's this kind of choice that means it's unlikely we'd include any one
> > > option in PostgreSQL, much like
> On Thu, Jun 06, 2024 at 12:53:38PM GMT, Alvaro Herrera wrote:
> On 2024-Jun-06, Dave Page wrote:
>
> > It's this kind of choice that means it's unlikely we'd include any one
> > option in PostgreSQL, much like various other tools such as failover
> > managers or poolers.
>
> TBH I see that more a
On 2024-Jun-06, Dave Page wrote:
> It's this kind of choice that means it's unlikely we'd include any one
> option in PostgreSQL, much like various other tools such as failover
> managers or poolers.
TBH I see that more as a bug than as a feature, and I see the fact that
there are so many schedul
On 6/6/2024 16:04, Wang Cheng wrote:
Noted. Thanks for suggestions. We will open-source it as an extension.
It would be nice! `For me doesn't matter where to contribute: to
PostgreSQL core or to its extension if it is published under BSD license.
--
regards, Andrei Lepikhov
Noted. Thanks for suggestions. We will open-source it as an extension.
Regards,
Cheng
-- Original --
From:
"Dave Page"
On Thu, 6 Jun 2024 at 09:47, Laurenz Albe wrote:
> On Thu, 2024-06-06 at 16:27 +0800, Wang Cheng wrote:
> > 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,
On Thu, 2024-06-06 at 16:27 +0800, Wang Cheng wrote:
> 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
> comm
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 c
13 matches
Mail list logo
