Re: elegant and effective way for running jobs inside a database

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Christopher Browne <cbbrowne(at)gmail(dot)com>
Cc: Artur Litwinowicz <admin(at)ybka(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: elegant and effective way for running jobs inside a database
Date: 2012-03-06 17:47:00
Message-ID: CA+TgmoYfrXsBA3L2G4+D5dwBcoHfsti9zc+=O3AJPH4qiORv8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 6, 2012 at 12:37 PM, Christopher Browne <cbbrowne(at)gmail(dot)com> wrote:
> On Tue, Mar 6, 2012 at 12:20 PM, Artur Litwinowicz <admin(at)ybka(dot)com> wrote:
>> Algorithm for first loop:
>> check jobs exists and is time to run it
>>   run job as other sql statements (some validity check may be done)
>>   get next job
>> no jobs - delay
>
> There are crucial things missing here, namely the need to establish at
> least one database connection in order to be able to check for the
> existence of jobs, as well as to establish additional connections as
> contexts in which to run jobs.
>
> That implies the need for some New Stuff that isn't quite the same as
> what we have within server processes today.
>
> There is nothing horrible about this; just that there's some extra
> mechanism that needs to come into existence in order to do this.

And also some interface. It'd be useful to have background jobs that
executed either immediately or at a certain time or after a certain
delay, as well as repeating jobs that execute at a certain interval or
on a certain schedule. Figuring out what all that should look like
is, well, part of the work that someone has to do.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2012-03-06 17:50:24 Re: Checksums, state of play
Previous Message Robert Haas 2012-03-06 17:44:19 Re: Checksums, state of play