From: | Sim Zacks <sim(at)compulab(dot)co(dot)il> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Alarm function in PL/pgSQL |
Date: | 2011-07-21 09:36:50 |
Message-ID: | 4E27F332.7040507@compulab.co.il |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 07/19/2011 01:35 AM, Jon Smark wrote:
> Hi,
>
>> I don't think this is really possible with postgres PLs generally.
>> Typically what you have to do is have a function that is called on an
>> interval that checks for alarms and runs them.
> Thanks for the prompt reply. Just to clarify: you are saying that the
> function that is called with a given periodicity must be so from *outside*
> PG, ie, from the client application, right? I mean, there is no way
> strictly internal to PG to have a function be called every given number
> of seconds?
>
> Cheers,
> Jon
Hi Jon,
The generally accepted way of doing this is to have a cron job (outside
of the database) calling a function which checks a polling table for
things it should process. What you would do is put the time you want a
row processed at and then your cron job will call a function that
processes all rows that are overdue.
Pg Agent will do that same thing as a cron job, as Craig mentioned.
Sim
From | Date | Subject | |
---|---|---|---|
Next Message | Jenish Vyas | 2011-07-21 10:00:37 | Maximum number of client connection supported by Postgres 8.4.6 |
Previous Message | Sofer, Yuval | 2011-07-21 06:56:51 | Re: compile postgres with visual studio 2010 |