Re: elegant and effective way for running jobs inside a database
Merlin Moncure <mmoncure@gmail.com>
From: Merlin Moncure <mmoncure@gmail.com>
To: Dimitri Fontaine <dimitri@2ndquadrant.fr>
Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2012-03-06T21:56:19Z
Lists: pgsql-hackers
On Tue, Mar 6, 2012 at 3:44 PM, Dimitri Fontaine <dimitri@2ndquadrant.fr> wrote: > Josh Berkus <josh@agliodbs.com> writes: >> Activity and discretion beyond that could be defined in PL code, >> including run/don't run conditions, activities, and dependancies. The >> only thing Postgres doesn't currently have is a clock which fires >> events. Anything we try to implement which is more complex than the >> above is going to not work for someone. And the pg_agent could be >> adapted easily to use the Postgres clock instead of cron. > > Oh, you mean like a ticker? If only we knew about a project that did > implement a ticker, in C, using the PostgreSQL licence, and who's using > it in large scale production. While at it, if such a ticker could be > used to implement job queues… > > https://github.com/markokr/skytools/tree/master/sql/ticker right -- exactly. it would be pretty neat if the database exposed this or a similar feature somehow -- perhaps by having the ticker send a notify? then a scheduler could sit on top of it without any dependencies on the host operating system. merlin