From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "David E(dot) Wheeler" <david(at)justatheory(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-09 18:51:37 |
Message-ID: | 4F5A5139.1020701@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 03/09/2012 01:40 PM, Robert Haas wrote:
> On Fri, Mar 9, 2012 at 12:02 PM, David E. Wheeler<david(at)justatheory(dot)com> wrote:
>> On Mar 9, 2012, at 7:55 AM, Merlin Moncure wrote:
>>> 100% agree (having re-read the thread and Alvaro's idea having sunk
>>> in). Being able to set up daemon processes side by side with the
>>> postmaster would fit the bill nicely. It's pretty interesting to
>>> think of all the places you could go with it.
>> pgAgent could use it *right now*. I keep forgetting to restart it after restarting PostgreSQL and finding after a day or so that no jobs have run.
> That can and should be fixed by teaching pgAgent that failing to
> connect to the server, or getting disconnected, is not a fatal error,
> but a reason to sleep and retry.
Yeah. It's still not entirely clear to me what a postmaster-controlled
daemon is going to be able to do that an external daemon can't.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-03-09 19:14:41 | Rules containing INSERT/UPDATE lack dependencies on target columns |
Previous Message | Robert Haas | 2012-03-09 18:40:36 | Re: elegant and effective way for running jobs inside a database |