On Mon, 2012-04-09 at 09:03 +, Jasen Betts wrote:
> On 2012-03-09, Bret Stern wrote:
> > We have a concrete batching application composed of two parts.
> > 1. The Monitor.
> > The Monitor cycles every 60 seconds, and looks into a Postgresql table
> > for jobs to run. Primarily these jobs upda
On 2012-03-09, Bret Stern wrote:
> We have a concrete batching application composed of two parts.
> 1. The Monitor.
> The Monitor cycles every 60 seconds, and looks into a Postgresql table
> for jobs to run. Primarily these jobs update Postgresql tables with
> data from external applications.
>
>
Yes, can do. Just have an insert trigger on the jobs table that notifies the
monitor, something like:
CREATE OR REPLACE FUNCTION notify_monitor()
RETURNS TRIGGER
LANGUAGE plpgsql
AS $$
BEGIN
NOTIFY monitor;
RETURN NULL;
END
$$
CREATE TRIGGER jobs_trigger
AFTER INSERT
ON
On Fri, Mar 9, 2012 at 8:53 AM, Bret Stern
wrote:
> We have a concrete batching application composed of two parts.
> 1. The Monitor.
> The Monitor cycles every 60 seconds, and looks into a Postgresql table
> for jobs to run. Primarily these jobs update Postgresql tables with
> data from external a
We have a concrete batching application composed of two parts.
1. The Monitor.
The Monitor cycles every 60 seconds, and looks into a Postgresql table
for jobs to run. Primarily these jobs update Postgresql tables with
data from external applications.
2. The Client.
The client schedules orders etc
