| From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Josh Berkus <josh(at)agliodbs(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: elegant and effective way for running jobs inside a database |
| Date: | 2012-03-06 23:12:25 |
| Message-ID: | CAFNqd5WCz0-=DXJyK-6td3j1bZa2TzW0zBpQN=ymV9ob0Vd50w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 6, 2012 at 5:01 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Why do we need a ticker? Just fetch the time of the task closest in the
> future, and sleep till that time or a notify arrives (meaning schedule
> change).
Keep in mind that cron functionality also includes "batch", which
means that the process needs to have the ability to be woken up by the
need to handle some pressing engagement that comes in suddenly.
For some events to be initiated by a NOTIFY received by a LISTENing
batch processor would be pretty slick...
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2012-03-06 23:25:55 | Re: Command Triggers, patch v11 |
| Previous Message | Tom Lane | 2012-03-06 22:53:00 | Re: elegant and effective way for running jobs inside a database |